tomoaki/hakorune
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
0a29f1443efa68106008b475b92e53ff20792c26
hakorune/docs/development/current/main/10-Now.md

336 lines
19 KiB
Markdown
Raw Normal View History

docs(current_task): add structured tasks under docs/current_task/{main,llvm,self_current_task} and unignore path
2025-09-08 11:35:30 +09:00
# Self Current Task — Now (main)
test: Phase 115 if-only call result merge parity (VM + LLVM EXE) Phase 115実装 - if分岐内での関数呼び出し結果をマージするパターンを固定 **実装内容**: - Fixture: phase115_if_only_call_merge_min.hako (expected: 2, 3) - if/else両分岐で関数呼び出し f() の結果を変数 v に代入 - if後にマージされた v を使用（LLVM EXE でのPHI node生成を検証） - VM smoke: phase115_if_only_call_merge_vm.sh - NYASH_DISABLE_PLUGINS=1 HAKO_JOINIR_STRICT=1 で実行 - LLVM EXE smoke: phase115_if_only_call_merge_llvm_exe.sh - llvm_exe_runner.sh を利用した標準パリティ検証 **検証結果**: - VM test: PASS ✅ - LLVM EXE test: PASS ✅ - Phase 114 regression: PASS ✅ **箱化モジュール化の観点**: - 単一責任: 各smokeは1パターンのみ検証（call result merge） - 分離: VM/LLVM EXEで独立したテスト（llvm_exe_runner.sh経由） - Fail-Fast: HAKO_JOINIR_STRICT=1 で不正な制御フローを即座に検出 **関連**: - Phase 103: If-Only基本パリティ（制御フロー基礎） - Phase 113: If-Only部分代入パリティ（変数マージ） - Phase 114: If-Only return+post パリティ（early returnとpost-if文） - Phase 115: If-Only call result merge パリティ（関数呼び出し結果マージ） ← 今回 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-18 02:32:08 +09:00
## 2025-12-18：Phase 115 完了 ✅
**Phase 115: if-only call result merge parity**
- if-only で関数呼び出し結果を merge するパターンを VM/LLVM で固定
- Fixture: phase115_if_only_call_merge_min.hako (expected: 2, 3)
- Smoke: VM + LLVM EXE parity 検証済み
- 回帰: Phase 103/113/114 維持確認
- 入口: `docs/development/current/main/phases/phase-115/README.md`
test: Phase 114 if-only return+post parity (VM + LLVM EXE) Phase 114 validates that if-only lowering correctly handles cases with: - Early return in the if-only branch - Post-if statements that execute on the else path - Different return values from each path Fixture: apps/tests/phase114_if_only_return_then_post_min.hako - Expected output: 7\n2 - f(1): condition true → early return 7 - f(0): condition false → x=1+1=2, return 2 Testing: - VM backend: phase114_if_only_return_then_post_vm.sh ✅ - LLVM EXE backend: phase114_if_only_return_then_post_llvm_exe.sh ✅ - Regression: Phase 103/113 maintained ✅ Implementation: No new code required - validates existing if-only exit line routing and post-if statement processing. Documentation: - docs/development/current/main/phases/phase-114/README.md - Updated: 10-Now.md, 01-JoinIR-Selfhost-INDEX.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-18 02:18:57 +09:00
## 2025-12-18：Phase 114 完了 ✅
**Phase 114: if-only return+post parity**
- if-only で early return + post-if statements パターンを VM/LLVM で固定
- Fixture: phase114_if_only_return_then_post_min.hako (expected: 7, 2)
- Smoke: VM + LLVM EXE parity 検証済み
- 回帰: Phase 103/113 維持確認
- 入口: `docs/development/current/main/phases/phase-114/README.md`
docs: Phase 113 if-only partial assign parity - Create phases/phase-113/README.md (background, fixed pattern, verification) - Update 10-Now.md with Phase 113 completion - Update 01-JoinIR-Selfhost-INDEX.md with Phase 113 entry 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-18 01:58:56 +09:00
## 2025-12-18：Phase 113 完了 ✅
**Phase 113: if-only partial assign parity**
- if-only（else なし）の片側代入で「保持 merge」パターンを VM/LLVM で固定
- Fixture: phase113_if_only_partial_assign_min.hako
- Smoke: VM + LLVM EXE parity 検証済み
docs: note Phase 110-112 control_tree status - Update 10-Now.md with Phase 112 completion - Note: StepTree capability guard (strict-only) implemented - Note: Default behavior unchanged, only affects HAKO_JOINIR_STRICT=1 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-18 01:39:06 +09:00
## 2025-12-18：Phase 112 完了 ✅
**Phase 112: StepTree Capability Guard (strict-only)**
- StepTree の required_caps を strict mode でチェック
- Allowlist: If, NestedIf, Loop, Return, Break, Continue
- Deny (strict): NestedLoop, TryCatch, Throw, Lambda, While, ForRange, Match, Arrow
- Error format: `[joinir/control_tree/cap_missing/<Cap>] <msg> Hint: <hint>`
- Default behavior unchanged (strict=false always Ok)
- 入口: `docs/development/current/main/design/control-tree.md`
- 実装:
- `src/mir/builder/control_flow/joinir/control_tree_capability_guard.rs`
- `src/mir/builder/calls/lowering.rs` (wired into lower_function_body)
## 2025-12-18：Phase 111 完了 ✅
**Phase 111: StepTreeContract + StepTreeSignature（dev-only）**
- StepTreeContract を追加（`exits` / `writes` / `required_caps` / `cond_sig`）
- StepTreeSignature を追加（`signature_basis_string()` を安定 hash、Span は含めない）
- dev-only parity を break/continue に加えて return まで拡張
- 入口: `docs/development/current/main/design/control-tree.md`
- 実装: `src/mir/control_tree/step_tree.rs`
## 2025-12-18：Phase 110 完了 ✅
**Phase 110: ControlTree / StepTree（構造SSOT・dev-only観測）**
- StepTree の語彙（Block/If/Loop/Stmt）と Feature を pure AST で実装（ValueId/PHI/CFG を混ぜない）
- joinir routing 側で extractor との “分類矛盾” を dev-only で検出（strict のみ Fail-Fast）
- 関数本体の StepTree を dev-only でダンプ（既定挙動不変）
- 入口: `docs/development/current/main/design/control-tree.md`
- 実装:
- `src/mir/control_tree/step_tree.rs`
- `src/mir/builder/calls/lowering.rs`
- `src/mir/builder/control_flow/joinir/routing.rs`
docs: Phase 109 DONE - Create phases/phase-109/README.md - Update 10-Now.md with completion report 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-17 23:45:55 +09:00
## 2025-12-17：Phase 109 完了 ✅
**Phase 109: error_tags hints SSOT**
- policy/validator エラーを "tag + message + hint" 形式に統一
- freeze_with_hint() API 追加（hint 必須、空なら panic）
- Phase 107/104/100 の代表3箱を hint 対応に移行
- 入口: `docs/development/current/main/phases/phase-109/README.md`
test(joinir): Phase 104 read_digits loop(true) parity
2025-12-17 18:29:27 +09:00
## 2025-12-17：Phase 104 完了 ✅
**Phase 104: loop(true) + break-only digits（read_digits 系）**
- read_digits_from 形の `loop(true)` を Pattern2 で受理（loop var 抽出 + break cond 正規化）
- fixture: `apps/tests/phase104_read_digits_loop_true_min.hako`（expected: `2`, `1`）
- smoke: `tools/smokes/v2/profiles/integration/apps/phase104_read_digits_vm.sh` / `tools/smokes/v2/profiles/integration/apps/phase104_read_digits_llvm_exe.sh`
docs: update Phase104 status and JoinIR map
2025-12-17 21:47:37 +09:00
- P2: json_cur 由来の回帰面を追加（fixture+VM/LLVM EXE smoke）
test(joinir): Phase 104 read_digits loop(true) parity
2025-12-17 18:29:27 +09:00
docs: add Phase 107 to Now/INDEX and backlog
2025-12-17 23:15:57 +09:00
## 2025-12-17：Phase 107 完了 ✅
**Phase 107: json_cur find_balanced_* depth scan（VM + LLVM EXE parity）**
- depth scan + nested if + return-in-loop を Pattern2 policy で受理（hardcode なし）
- fixture:
- `apps/tests/phase107_find_balanced_array_end_min.hako`（expected: `1`, `3`）
- `apps/tests/phase107_find_balanced_object_end_min.hako`（expected: `1`, `3`）
- smoke（integration）:
- VM: `tools/smokes/v2/profiles/integration/apps/phase107_find_balanced_array_end_vm.sh` / `tools/smokes/v2/profiles/integration/apps/phase107_find_balanced_object_end_vm.sh`
- LLVM EXE: `tools/smokes/v2/profiles/integration/apps/phase107_find_balanced_array_end_llvm_exe.sh` / `tools/smokes/v2/profiles/integration/apps/phase107_find_balanced_object_end_llvm_exe.sh`
- 入口: `docs/development/current/main/phases/phase-107/README.md`
docs: Phase 109 DONE - Create phases/phase-109/README.md - Update 10-Now.md with completion report 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-17 23:45:55 +09:00
## 2025-12-17：Phase 108 完了 ✅
**Phase 108: Pattern2 policy router SSOT（薄い入口の固定）**
- post-loop early return を一般 plan（`cond`/`ret_expr`）として独立し、Pattern2Inputs の依存を解消
- ApplyPolicyStepBox から “直叩き” を撤去し、policy router 1本に集約（入口SSOT）
- 入口: `docs/development/current/main/phases/phase-108/README.md`
docs: Phase 103 DONE (if-only parity smokes)
2025-12-17 17:41:10 +09:00
## 2025-12-17：Phase 103 P0 完了 ✅
**Phase 103: if-only regression baseline**
- if-only（loop無し）の nested if + merge を fixture 化し、VM/LLVM EXE parity を integration smoke で固定
docs: Phase 103 plan (if-only parity baseline)
2025-12-17 17:39:12 +09:00
## 2025-12-17：Phase 100 P3 完了 ✅
**Phase 100 P3: String Accumulator Captures**
- String accumulator（`out = out + ch`）を最小形で固定し、VM/LLVM EXE parity を smoke で検証
- LLVM EXE 側の stringish 伝播（PHI/copy/binop）を修正し、concat の意味論を安定化
docs: Phase 100 P2.1 - LLVM EXE parity for mutable accumulator - Update phases/phase-100/README.md with LLVM EXE smoke note - Update 10-Now.md with P2.1 short report 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-17 06:31:21 +09:00
## 2025-12-17：Phase 100 P2 完了 ✅
**Phase 100 P2: Mutable Accumulator Captures**
- Mutable accumulator pattern (`out = out + ch`) を Pattern2 carrier で対応
- ScopeManager 委譲により read-only check を回避
- Numeric output validation (count=3) で fixture 固定
- VM/LLVM EXE parity 完了（smoke 追加）
docs: Phase 100 P1 pinned receiver integration tests complete - Update docs/development/current/main/phases/phase-100/README.md * Document P1 implementation and pinned receiver example - Update docs/development/current/main/10-Now.md * Add Phase 100 P1 completion short report 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2025-12-17 05:43:54 +09:00
## 2025-12-17：Phase 100 P1 完了 ✅
**Phase 100 P1: Pinned Local Captures**
- CapturedEnv に CapturedKind (Explicit/Pinned) 拡張
- PinnedLocalAnalyzer で loop-outer read-only locals を識別
- Pinned receiver (例: s.substring()) が loop 内で使用可能に
- Fixture/smoke で動作確認済み
docs: Phase 99 notes and indices Trim/escape実コード寄り強化の記録: - phase-96: 3ケース追記 - phase-95: 末尾バックスラッシュ扱い追記 - phase-99: 新規README作成 - 10-Now.md: Phase 99短報追加 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-17 04:26:23 +09:00
## 2025‑12‑17：Phase 99 完了 ✅
**Phase 99: Trim/escape 実コード寄り強化（VM+LLVM EXE）**
- next_non_ws を3ケース固定（`2`, `-1`, `3`）— 改行/CR/Tab混在パターン追加
- escape 末尾バックスラッシュを best-effort として固定（`hello\` そのまま出力）
- VM+LLVM EXE parity 完全対応、integration smoke で検証済み
docs: Phase 103 plan (if-only parity baseline)
2025-12-17 17:39:12 +09:00
関連（設計/実装の入口）:
- Phase 100: `docs/development/current/main/phases/phase-100/README.md`
docs: Phase 100 pinned read-only captures plan
2025-12-17 05:03:07 +09:00
feat(llvm): Phase 132 - Pattern 1 exit value parity fix + Box-First refactoring ## Phase 132: Exit PHI Value Parity Fix ### Problem Pattern 1 (Simple While) returned 0 instead of final loop variable value (3) - VM: RC: 3 ✅ (correct) - LLVM: Result: 0 ❌ (wrong) ### Root Cause (Two Layers) 1. **JoinIR/Boundary**: Missing exit_bindings → ExitLineReconnector not firing 2. **LLVM Python**: block_end_values snapshot dropping PHI values ### Fix **JoinIR** (simple_while_minimal.rs): - Jump(k_exit, [i_param]) passes exit value **Boundary** (pattern1_minimal.rs): - Added LoopExitBinding with carrier_name="i", role=LoopState - Enables ExitLineReconnector to update variable_map **LLVM** (block_lower.py): - Use predeclared_ret_phis for reliable PHI filtering - Protect builder.vmap PHIs from overwrites (SSOT principle) ### Result - ✅ VM: RC: 3 - ✅ LLVM: Result: 3 - ✅ VM/LLVM parity achieved ## Phase 132-Post: Box-First Refactoring ### Rust Side **JoinModule::require_function()** (mod.rs): - Encapsulate function search logic - 10 lines → 1 line (90% reduction) - Reusable for Pattern 2-5 ### Python Side **PhiManager Box** (phi_manager.py - new): - Centralized PHI lifecycle management - 47 lines → 8 lines (83% reduction) - SSOT: builder.vmap owns PHIs - Fail-Fast: No silent overwrites **Integration**: - LLVMBuilder: Added phi_manager - block_lower.py: Delegated to PhiManager - tagging.py: Register PHIs with manager ### Documentation **New Files**: - docs/development/architecture/exit-phi-design.md - docs/development/current/main/investigations/phase132-llvm-exit-phi-wrong-result.md - docs/development/current/main/phases/phase-132/ **Updated**: - docs/development/current/main/10-Now.md - docs/development/current/main/phase131-3-llvm-lowering-inventory.md ### Design Principles - Box-First: Logic encapsulated in classes/methods - SSOT: Single Source of Truth (builder.vmap for PHIs) - Fail-Fast: Early explicit failures, no fallbacks - Separation of Concerns: 3-layer architecture 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-15 03:17:31 +09:00
## 2025‑12‑15：Phase 132 完了 ✅
**Phase 132: LLVM Exit PHI=0 根治修正 完了！**
- ループ exit PHI が 0 を返す問題を根治解決
- 原因（2層）: (1) JoinIR/Boundary が exit 値を境界に渡していない、(2) LLVM Python が PHI を落とす/上書きする
- 修正: Pattern 1 で exit 値を明示的に渡す + `predeclared_ret_phis` 使用 + `builder.vmap` の PHI 保護
- 結果: `/tmp/p1_return_i.hako` が 3 を返す（VM 一致）
- 詳細: `investigations/phase132-llvm-exit-phi-wrong-result.md`
feat(joinir): Phase 132-P3 - Exit PHI collision early detection Added verify_exit_phi_no_collision() to contract_checks.rs for early detection of ValueId collisions between exit PHIs and other instructions. Problem detected: - If exit_phi_builder uses builder.value_gen.next() (module-level) instead of func.next_value_id() (function-level), ValueIds can collide: Example: - bb0: %1 = const 0 (counter init) - bb3: %1 = phi ... (exit PHI - collision!) Previous behavior: - Error only detected at LLVM backend runtime - Cryptic error: "Cannot overwrite PHI dst=1" New behavior: - Panic at Rust compile time (debug build) - Clear error message with fix suggestion: "Exit PHI dst %1 collides with instruction in block 0 Fix: Use func.next_value_id() in exit_phi_builder.rs" Benefits: - 🔥 Fail-Fast: Catch errors during Rust compilation, not LLVM execution - 📋 Clear messages: Exact collision point + fix suggestion - 🧪 Testable: verify_exit_phi_no_collision() can be unit tested 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-15 06:00:48 +09:00
**追加（Phase 132-P2）: Case C の Exit PHI ValueId 衝突を修正**
- 原因: `exit_phi_builder.rs` が module-level allocator を使い、同一関数内で ValueId が衝突し得た
- 修正: `func.next_value_id()`（function-level）へ統一（`bd07b7f4`）
- 結果: `apps/tests/llvm_stage3_loop_only.hako` が LLVM EXE でも `Result: 3`（VM 一致）
- 詳細: `investigations/phase132-case-c-llvm-exe.md`
docs: Phase 132-P3 verifier note
2025-12-15 06:08:19 +09:00
**追加（Phase 132-P3）: Exit PHI collision の早期検出（debug-only）**
- `verify_exit_phi_no_collision()` を `contract_checks.rs` に追加し、ValueId 衝突を JoinIR merge の段階で Fail-Fast する
docs: add loop canonicalizer SSOT + MirBuilder entrypoint
2025-12-16 04:37:47 +09:00
## 2025‑12‑15：Phase 133–136（短報）
feat(joinir): Phase 135 P0 - ConditionLoweringBox allocator SSOT (ValueId collision fix) ## Summary Root cause: ConditionLoweringBox was bypassing ConditionContext.alloc_value (SSOT allocator), causing ValueId collisions between JoinIR condition params and lowered instructions. ## Changes 1. **ConditionLoweringBox (expr_lowerer.rs)**: Must use ConditionContext.alloc_value - Pass &mut ConditionContext to lower_condition (SSOT allocator) - Eliminates internal counter usage 2. **Allocator unification (condition_lowerer.rs, method_call_lowerer.rs)**: - Accept &mut dyn FnMut() -> ValueId as allocator parameter - Ensures all lowering paths use same SSOT allocator 3. **Boundary Copy deduplication (joinir_inline_boundary_injector.rs)**: - Deduplicate condition_bindings by dst - Fail-Fast if different sources target same dst (MIR SSA violation) 4. **Trim pattern fixes (trim_loop_lowering.rs, trim_pattern_validator.rs, stmts.rs)**: - Use builder.next_value_id() instead of value_gen.next() in function context - Ensures function-level ValueId allocation respects reserved PHI dsts ## Acceptance ✅ ./target/release/hakorune --verify apps/tests/phase133_json_skip_whitespace_min.hako ✅ Smoke: phase135_trim_mir_verify.sh - MIR SSA validation PASS ✅ Regression: phase132_exit_phi_parity.sh - 3/3 PASS ✅ Regression: phase133_json_skip_whitespace_llvm_exe.sh - compile-only PASS 🤖 Generated with Claude Code Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2025-12-15 18:49:08 +09:00
- Phase 133: promoted carrier（Trim）の `join_id` 解決を SSOT に寄せて修正（smoke は compile-only）。
- Phase 134: plugin loader best-effort loading を導入（決定的順序 + failure 集約 + 継続）。
- Phase 135: ConditionLoweringBox が allocator SSOT を無視して ValueId 衝突を起こす問題を根治。
- 詳細: `docs/development/current/main/phases/phase-135/README.md`
docs: add loop canonicalizer SSOT + MirBuilder entrypoint
2025-12-16 04:37:47 +09:00
- Phase 136: MirBuilder の Context 分割を完了し、状態の SSOT を Context に一本化。
- 詳細: `docs/development/current/main/phases/phase-136/README.md`
feat(joinir): Phase 135 P0 - ConditionLoweringBox allocator SSOT (ValueId collision fix) ## Summary Root cause: ConditionLoweringBox was bypassing ConditionContext.alloc_value (SSOT allocator), causing ValueId collisions between JoinIR condition params and lowered instructions. ## Changes 1. **ConditionLoweringBox (expr_lowerer.rs)**: Must use ConditionContext.alloc_value - Pass &mut ConditionContext to lower_condition (SSOT allocator) - Eliminates internal counter usage 2. **Allocator unification (condition_lowerer.rs, method_call_lowerer.rs)**: - Accept &mut dyn FnMut() -> ValueId as allocator parameter - Ensures all lowering paths use same SSOT allocator 3. **Boundary Copy deduplication (joinir_inline_boundary_injector.rs)**: - Deduplicate condition_bindings by dst - Fail-Fast if different sources target same dst (MIR SSA violation) 4. **Trim pattern fixes (trim_loop_lowering.rs, trim_pattern_validator.rs, stmts.rs)**: - Use builder.next_value_id() instead of value_gen.next() in function context - Ensures function-level ValueId allocation respects reserved PHI dsts ## Acceptance ✅ ./target/release/hakorune --verify apps/tests/phase133_json_skip_whitespace_min.hako ✅ Smoke: phase135_trim_mir_verify.sh - MIR SSA validation PASS ✅ Regression: phase132_exit_phi_parity.sh - 3/3 PASS ✅ Regression: phase133_json_skip_whitespace_llvm_exe.sh - compile-only PASS 🤖 Generated with Claude Code Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2025-12-15 18:49:08 +09:00
docs: mark loop canonicalizer Phase 137-141 complete
2025-12-16 07:54:33 +09:00
## 2025‑12‑16：Phase 137‑141（短報）
docs: update Phase 137-1 completion status and Phase 2 roadmap ## Summary Loop Canonicalizer Phase 1（型定義）の完了と、Phase 2（dev-only 観測）への ロードマップを記録。 ## Changes ### loop-canonicalizer.md - Status: Design (P0) → Phase 1 done（型定義まで） - 実装の入口を明記（src/mir/loop_canonicalizer/mod.rs） - NYASH_LOOP_ROUTING_TRACE → joinir_dev_enabled() に変更 （新 ENV を増やさず、既存のスイッチに寄せる） ### CURRENT_TASK.md - Phase 137-1 完了を追記 - P0 を「設計」→「Phase 2（dev-only 観測）」へ更新 ### phases/README.md - Phase 137 を追加 ### phases/phase-137/README.md (NEW) - Phase 1 完了サマリ - Phase 2 予定を最小で記録 ### joinir-design-map.md / 01-JoinIR-Selfhost-INDEX.md - loop-canonicalizer への導線を追加 ## Next Steps Phase 2: dev-only 観測の導入 - canonicalize_loop_expr() の薄い入口を追加 - joinir_dev_enabled() 配下でログ出し - 既定挙動は完全不変 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-16 05:10:29 +09:00
docs: mark loop canonicalizer Phase 137-141 complete
2025-12-16 07:54:33 +09:00
- Loop Canonicalizer（前処理 SSOT）は Phase 141 まで完了（既定挙動は不変、dev-only 観測/strict parity あり）。
docs: update Phase 137-1 completion status and Phase 2 roadmap ## Summary Loop Canonicalizer Phase 1（型定義）の完了と、Phase 2（dev-only 観測）への ロードマップを記録。 ## Changes ### loop-canonicalizer.md - Status: Design (P0) → Phase 1 done（型定義まで） - 実装の入口を明記（src/mir/loop_canonicalizer/mod.rs） - NYASH_LOOP_ROUTING_TRACE → joinir_dev_enabled() に変更 （新 ENV を増やさず、既存のスイッチに寄せる） ### CURRENT_TASK.md - Phase 137-1 完了を追記 - P0 を「設計」→「Phase 2（dev-only 観測）」へ更新 ### phases/README.md - Phase 137 を追加 ### phases/phase-137/README.md (NEW) - Phase 1 完了サマリ - Phase 2 予定を最小で記録 ### joinir-design-map.md / 01-JoinIR-Selfhost-INDEX.md - loop-canonicalizer への導線を追加 ## Next Steps Phase 2: dev-only 観測の導入 - canonicalize_loop_expr() の薄い入口を追加 - joinir_dev_enabled() 配下でログ出し - 既定挙動は完全不変 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-16 05:10:29 +09:00
- 設計 SSOT: `docs/development/current/main/design/loop-canonicalizer.md`
feat(mir): Loop Canonicalizer Phase 3 - skip_whitespace pattern recognition ## Summary skip_whitespace パターンを Skeleton→Decision で認識可能に。 dev-only 観測で chosen=Pattern3IfPhi / missing_caps=[] を固定。 ## Changes - src/mir/loop_canonicalizer/mod.rs: - try_extract_skip_whitespace_pattern() 追加 - loop(cond) { ... if check { p = p + 1 } else { break } } パターン認識 - carrier name, delta, body statements を抽出 - canonicalize_loop_expr() 拡張（skip_whitespace 対応） - Pattern3IfPhi 成功時は RoutingDecision::success 返却 - Skeleton に HeaderCond, Body, Update ステップ追加 - CarrierSlot に Counter role 設定 - ExitContract に has_break=true 設定 - Phase 3 unit tests 追加 - test_skip_whitespace_pattern_recognition: 基本パターン - test_skip_whitespace_with_body_statements: body 付きパターン - test_skip_whitespace_fails_without_else: else なし失敗 - test_skip_whitespace_fails_with_wrong_delta: 減算パターン失敗 - Phase 2 obsolete tests 削除 - src/mir/builder/control_flow/joinir/routing.rs: - Debug 出力拡張（chosen pattern 表示） ## Tests - cargo test --release --lib loop_canonicalizer::tests: PASS（11 tests） - cargo test --release --lib: PASS（1044 tests, 退行なし） - HAKO_JOINIR_DEBUG=1 test_pattern3_skip_whitespace.hako: - chosen=Pattern3IfPhi ✅ - missing_caps=[] ✅ ## Validation - ✅ dev-only 観測（HAKO_JOINIR_DEBUG=1）のときだけログ出力 - ✅ フラグ OFF 時は完全不変 - ✅ skip_whitespace パターンで SUCCESS 固定 - ✅ unit tests で全パターン固定 Phase 137-3 complete
2025-12-16 05:38:18 +09:00
- 実装: `src/mir/loop_canonicalizer/mod.rs`（+ 観測: `src/mir/builder/control_flow/joinir/routing.rs`）
docs: mark loop canonicalizer Phase 137-141 complete
2025-12-16 07:54:33 +09:00
- Phase 記録: `docs/development/current/main/phases/phase-137/README.md`
docs: update Phase 137-1 completion status and Phase 2 roadmap ## Summary Loop Canonicalizer Phase 1（型定義）の完了と、Phase 2（dev-only 観測）への ロードマップを記録。 ## Changes ### loop-canonicalizer.md - Status: Design (P0) → Phase 1 done（型定義まで） - 実装の入口を明記（src/mir/loop_canonicalizer/mod.rs） - NYASH_LOOP_ROUTING_TRACE → joinir_dev_enabled() に変更 （新 ENV を増やさず、既存のスイッチに寄せる） ### CURRENT_TASK.md - Phase 137-1 完了を追記 - P0 を「設計」→「Phase 2（dev-only 観測）」へ更新 ### phases/README.md - Phase 137 を追加 ### phases/phase-137/README.md (NEW) - Phase 1 完了サマリ - Phase 2 予定を最小で記録 ### joinir-design-map.md / 01-JoinIR-Selfhost-INDEX.md - loop-canonicalizer への導線を追加 ## Next Steps Phase 2: dev-only 観測の導入 - canonicalize_loop_expr() の薄い入口を追加 - joinir_dev_enabled() 配下でログ出し - 既定挙動は完全不変 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-16 05:10:29 +09:00
feat(mir): Phase 92 P2-2 - Body-local variable support for ConditionalStep Phase 92 P2-2完了：ConditionalStepのcondition（ch == '\\'など）でbody-local変数をサポート ## 主要変更 ### 1. condition_lowerer.rs拡張 - `lower_condition_to_joinir`に`body_local_env`パラメータ追加 - 変数解決優先度：ConditionEnv → LoopBodyLocalEnv - すべての再帰ヘルパー（comparison, logical_and, logical_or, not, value_expression）対応 ### 2. conditional_step_emitter.rs修正 - `emit_conditional_step_update`に`body_local_env`パラメータ追加 - condition loweringにbody-local環境を渡す ### 3. loop_with_break_minimal.rs修正 - break condition loweringをbody-local init の**後**に移動（line 411） - header_break_lowering::lower_break_conditionにbody_local_env渡す - emit_conditional_step_updateにbody_local_env渡す（line 620） ### 4. header_break_lowering.rs修正 - `lower_break_condition`に`body_local_env`パラメータ追加 - scope_managerにbody-local環境を渡す ### 5. 全呼び出し箇所修正 - expr_lowerer.rs (2箇所) - method_call_lowerer.rs (2箇所) - loop_with_if_phi_if_sum.rs (3箇所) - loop_with_continue_minimal.rs (1箇所) - carrier_update_emitter.rs (1箇所・legacy) ## アーキテクチャ改善 ### Break Condition Lowering順序修正 旧: Header → **Break Cond** → Body-local Init 新: Header → **Body-local Init** → Break Cond 理由：break conditionが`ch == '\"'`のようにbody-local変数を参照する場合、body-local initが先に必要 ### 変数解決優先度（Phase 92 P2-2） 1. ConditionEnv（ループパラメータ、captured変数） 2. LoopBodyLocalEnv（body-local変数like `ch`） ## テスト ### ビルド ✅ cargo build --release成功（30 warnings、0 errors） ### E2E ⚠️ body-local promotion問題でブロック（Phase 92範囲外） - Pattern2はbody-local変数をcarrier promotionする必要あり - 既存パターン（A-3 Trim, A-4 DigitPos）に`ch = get_char(i)`が該当しない - **Phase 92 P2-2目標（condition loweringでbody-local変数サポート）は達成** ## 次タスク（Phase 92 P3以降） - body-local variable promotion拡張（Pattern2で`ch`のような変数を扱う） - P5b E2Eテスト完全動作確認 ## Phase 92 P2-2完了 ✅ Body-local変数のcondition lowering対応完了 ✅ ConditionalStepでbody-local変数参照可能 ✅ Break condition lowering順序修正
2025-12-16 17:08:15 +09:00
## 2025‑12‑16：Phase 92（短報）
docs(phase93): Phase 93 P0完了記録 & ドキュメント整理 ## 追加 - docs/development/current/main/phases/phase-93/README.md - Phase 93 P0 (ConditionOnly Derived Slot) 完了記録 - 実装内容・テスト結果の詳細 ## 更新 - CURRENT_TASK.md: Phase 93 P0完了に伴う更新 - 10-Now.md: 現在の進捗状況更新 - 30-Backlog.md: Phase 92/93関連タスク整理 - phase-91/92関連ドキュメント: historical化・要約化 ## 削減 - 735行削減（historical化により詳細をREADMEに集約） 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-16 23:30:39 +09:00
- Phase 92（ConditionalStep / P5b escape の lowering 基盤）は完了。
- 条件付き更新（`ConditionalStep`）のJoinIR表現 + Pattern2 側の委譲（emitter 箱化）
- 条件式での body-local 参照（`ConditionEnv → LoopBodyLocalEnv`）+ 最小E2E smoke 固定
- Phase 記録（SSOT入口）: `docs/development/current/main/phases/phase-92/README.md`
- 残: P5b の “完全E2E” は body-local promotion 拡張後（スコープ外で保留）
## 2025‑12‑16：Phase 93（短報）
- Trim の `is_ch_match` など「ConditionOnly（PHIで運ばない派生値）」を Derived Slot として毎イテレーション再計算できるようにした。
- SSOT: `ConditionOnlyRecipe`（運搬禁止）+ `ConditionOnlyEmitter`
- schedule: `body-init → derived → break` を評価順SSOTとして強制
- Phase 記録（入口）: `docs/development/current/main/phases/phase-93/README.md`
feat(mir): Phase 92 P2-2 - Body-local variable support for ConditionalStep Phase 92 P2-2完了：ConditionalStepのcondition（ch == '\\'など）でbody-local変数をサポート ## 主要変更 ### 1. condition_lowerer.rs拡張 - `lower_condition_to_joinir`に`body_local_env`パラメータ追加 - 変数解決優先度：ConditionEnv → LoopBodyLocalEnv - すべての再帰ヘルパー（comparison, logical_and, logical_or, not, value_expression）対応 ### 2. conditional_step_emitter.rs修正 - `emit_conditional_step_update`に`body_local_env`パラメータ追加 - condition loweringにbody-local環境を渡す ### 3. loop_with_break_minimal.rs修正 - break condition loweringをbody-local init の**後**に移動（line 411） - header_break_lowering::lower_break_conditionにbody_local_env渡す - emit_conditional_step_updateにbody_local_env渡す（line 620） ### 4. header_break_lowering.rs修正 - `lower_break_condition`に`body_local_env`パラメータ追加 - scope_managerにbody-local環境を渡す ### 5. 全呼び出し箇所修正 - expr_lowerer.rs (2箇所) - method_call_lowerer.rs (2箇所) - loop_with_if_phi_if_sum.rs (3箇所) - loop_with_continue_minimal.rs (1箇所) - carrier_update_emitter.rs (1箇所・legacy) ## アーキテクチャ改善 ### Break Condition Lowering順序修正 旧: Header → **Break Cond** → Body-local Init 新: Header → **Body-local Init** → Break Cond 理由：break conditionが`ch == '\"'`のようにbody-local変数を参照する場合、body-local initが先に必要 ### 変数解決優先度（Phase 92 P2-2） 1. ConditionEnv（ループパラメータ、captured変数） 2. LoopBodyLocalEnv（body-local変数like `ch`） ## テスト ### ビルド ✅ cargo build --release成功（30 warnings、0 errors） ### E2E ⚠️ body-local promotion問題でブロック（Phase 92範囲外） - Pattern2はbody-local変数をcarrier promotionする必要あり - 既存パターン（A-3 Trim, A-4 DigitPos）に`ch = get_char(i)`が該当しない - **Phase 92 P2-2目標（condition loweringでbody-local変数サポート）は達成** ## 次タスク（Phase 92 P3以降） - body-local variable promotion拡張（Pattern2で`ch`のような変数を扱う） - P5b E2Eテスト完全動作確認 ## Phase 92 P2-2完了 ✅ Body-local変数のcondition lowering対応完了 ✅ ConditionalStepでbody-local変数参照可能 ✅ Break condition lowering順序修正
2025-12-16 17:08:15 +09:00
feat(joinir): Phase 94 - P5b escape full E2E (derived ch + +1/+2)
2025-12-17 00:59:33 +09:00
## 2025‑12‑16：Phase 94（短報）
- P5b escape（`ch` 再代入 + `i` の +1/+2）を “derived（Select）” として扱い、VM E2E を固定。
- 新箱: `BodyLocalDerivedEmitter` + 明示ポリシー（strict で理由付き Fail-Fast）
- integration smoke: `tools/smokes/v2/profiles/integration/apps/phase94_p5b_escape_e2e.sh`
- Phase 記録（入口）: `docs/development/current/main/phases/phase-94/README.md`
docs: add phase95 json_loader escape entry
2025-12-17 01:01:16 +09:00
## 2025‑12‑16：Phase 95（短報）
- MiniJsonLoader の escape ループを Phase 94 基盤で固定（派生 body-local + 条件付き skip）。
- フィクスチャ: `apps/tests/phase95_json_loader_escape_min.hako`
- smoke: `tools/smokes/v2/profiles/integration/apps/phase95_json_loader_escape_vm.sh`
- Phase 記録（入口）: `docs/development/current/main/phases/phase-95/README.md`
test: add phase96 trim loop fixture and smoke
2025-12-17 01:25:06 +09:00
## 2025‑12‑16：Phase 96（短報）
- Trim系 policy 化を開始し、MiniJsonLoader の next_non_ws ループを fixtures/smoke に追加。
- フィクスチャ: `apps/tests/phase96_json_loader_next_non_ws_min.hako`
- smoke: `tools/smokes/v2/profiles/integration/apps/phase96_json_loader_next_non_ws_vm.sh`
- Phase 記録（入口）: `docs/development/current/main/phases/phase-96/README.md`
docs: add Phase 97 LLVM EXE parity entry
2025-12-17 02:26:42 +09:00
## 2025‑12‑16：Phase 97（短報）
- Phase 95/96 の MiniJsonLoader fixture を LLVM EXE ラインでも固定し、JoinIR/Trim の退行検出を強化。
- smoke: `tools/smokes/v2/profiles/integration/apps/phase97_next_non_ws_llvm_exe.sh`（next_non_ws）
- smoke: `tools/smokes/v2/profiles/integration/apps/phase97_json_loader_escape_llvm_exe.sh`（escape）
- Phase 記録（入口）: `docs/development/current/main/phases/phase-97/README.md`
feat(llvm): Phase 97 Box/Policy refactoring complete Box化完了: - CallRoutePolicyBox: Call routing SSoT - PrintArgMarshallerBox: Print marshalling SSoT - TypeFactsBox: Type propagation SSoT - PhiSnapshotPolicyBox: PHI contract SSoT - PluginErrorContext: Structured error reporting 📋 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-17 04:14:26 +09:00
## 2025‑12‑17：Phase 98（短報）
- plugin loader に strict fail-fast を導入し（HAKO_JOINIR_STRICT=1）、FileBox/MapBox の LLVM EXE parity を持続可能に。
- smoke: `tools/smokes/v2/profiles/integration/apps/phase97_next_non_ws_llvm_exe.sh`
- smoke: `tools/smokes/v2/profiles/integration/apps/phase97_json_loader_escape_llvm_exe.sh`
- Phase 記録（入口）: `docs/development/current/main/phases/phase-98/README.md`
docs: Phase 102 entry (real-app regression smokes)
2025-12-17 16:57:15 +09:00
## 2025‑12‑17：Phase 102（短報）
- real-app（MiniJsonLoader.read_quoted_from）の loop を最小抽出し、VM + LLVM EXE で regression を固定（期待: length=4）。
- フィクスチャ: `apps/tests/phase102_realapp_read_quoted_min.hako`
- smoke: `tools/smokes/v2/profiles/integration/apps/phase102_realapp_read_quoted_vm.sh`
- smoke: `tools/smokes/v2/profiles/integration/apps/phase102_realapp_read_quoted_llvm_exe.sh`
- Phase 記録（入口）: `docs/development/current/main/phases/phase-102/README.md`
docs(phase131): LLVM SSOT強化 + ConsoleBox調査完了 + Phase86-90要約 Phase 131-1 完了: LLVM exe line SSOT 強化 - phase87-selfhost-llvm-exe-line.md に 4セクション追加（+300行） - 環境変数リファレンス（14変数） - 成功/失敗基準（exit code 0/1/2/3） - コンパイラモード説明（harness vs crate） - デバッグセクション拡張 - "1コマンドで再現" 可能な状態を確立 Phase 131-2 完了: ConsoleBox 問題調査 - VM の 3重登録経路を特定（BoxFactoryRegistry/UnifiedRegistry/Builtin） - LLVM backend は Phase 133 で解決済み - 3つのドキュメント作成: - phase131-2-consolebox-investigation.md（詳細調査） - phase131-2-summary.md（エグゼクティブサマリ） - phase131-2-box-resolution-map.md（Box 解決マップ） Phase 86-90 完了: Loop frontends 要約 - phase86-90-loop-frontends-summary.md 追加 - Pattern4/ContinueReturn/ParseStringComposite の経緯を1枚に集約 - INDEX から導線追加 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 05:24:31 +09:00
## 2025‑12‑14：現状サマリ
feat(joinir): Phase 171-fix ConditionEnv/ConditionBinding architecture Proper HOST↔JoinIR ValueId separation for condition variables: - Add ConditionEnv struct (name → JoinIR-local ValueId mapping) - Add ConditionBinding struct (HOST/JoinIR ValueId pairs) - Modify condition_to_joinir to use ConditionEnv instead of builder.variable_map - Update Pattern2 lowerer to build ConditionEnv and ConditionBindings - Extend JoinInlineBoundary with condition_bindings field - Update BoundaryInjector to inject Copy instructions for condition variables This fixes the undefined ValueId errors where HOST ValueIds were being used directly in JoinIR instructions. Programs now execute (RC: 0), though loop variable exit values still need Phase 172 work. Key invariants established: 1. JoinIR uses ONLY JoinIR-local ValueIds 2. HOST↔JoinIR bridging is ONLY through JoinInlineBoundary 3. condition_to_joinir NEVER accesses builder.variable_map 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-07 01:45:03 +09:00
docs: ドキュメント配置ルール（SSOT）確立 ## 追加内容 - CLAUDE.md にドキュメント配置ルール（SSOT）セクション追加 - DOCS_LAYOUT.md (SSOT): 置き場所ルール定義 - phases/README.md: Phase ドキュメント説明 - design/README.md: 設計図ドキュメント説明 - investigations/README.md: 調査ログ説明 ## ルール概要 1. **Phase 文書** → phases/phase-<N>/ 2. **設計図** → design/ 3. **調査ログ** → investigations/ （結論を 10-Now/20-Decisions に反映） ## 導線 - CLAUDE.md で概要説明 - DOCS_LAYOUT.md で詳細定義（SSOT） - 各フォルダ README で参照方法 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2025-12-14 18:27:24 +09:00
（補足）docs が増えて迷子になったときの「置き場所ルール（SSOT）」:
- `docs/development/current/main/DOCS_LAYOUT.md`
feat(joinir): Phase 171-fix ConditionEnv/ConditionBinding architecture Proper HOST↔JoinIR ValueId separation for condition variables: - Add ConditionEnv struct (name → JoinIR-local ValueId mapping) - Add ConditionBinding struct (HOST/JoinIR ValueId pairs) - Modify condition_to_joinir to use ConditionEnv instead of builder.variable_map - Update Pattern2 lowerer to build ConditionEnv and ConditionBindings - Extend JoinInlineBoundary with condition_bindings field - Update BoundaryInjector to inject Copy instructions for condition variables This fixes the undefined ValueId errors where HOST ValueIds were being used directly in JoinIR instructions. Programs now execute (RC: 0), though loop variable exit values still need Phase 172 work. Key invariants established: 1. JoinIR uses ONLY JoinIR-local ValueIds 2. HOST↔JoinIR bridging is ONLY through JoinInlineBoundary 3. condition_to_joinir NEVER accesses builder.variable_map 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-07 01:45:03 +09:00
### JoinIR / Loop / If ライン
- LoopBuilder は Phase 186‑187 で完全削除済み。**JoinIR が唯一の loop lowering 経路**。
- LoopPattern 系は Pattern1–4 まで実装・本線化済み：
- Pattern1: Simple While
- Pattern2: Loop with Break
- Pattern3: Loop with If‑Else PHI（break/continue なし）
- Pattern4: Loop with Continue（multi‑carrier 対応）
- Exit/Carrier/Boundary ラインは次の箱で SSOT 化：
- `CarrierInfo` / `ExitMeta` / `ExitBindingBuilder`
- `JoinInlineBoundary` + `LoopExitBinding`
- If lowering は IfSelectLowerer/IfMergeLowerer を中心に整理済み。Select/PHI の扱いも Phase 189 系で橋渡し済み。
- 残課題（JoinIR ライン）：
- JoinIR→MIR merge の一般化（複雑な Select/PHI パターンの統合）
- JsonParserBox など実アプリ側での長期運用テスト
docs(phase131): LLVM SSOT強化 + ConsoleBox調査完了 + Phase86-90要約 Phase 131-1 完了: LLVM exe line SSOT 強化 - phase87-selfhost-llvm-exe-line.md に 4セクション追加（+300行） - 環境変数リファレンス（14変数） - 成功/失敗基準（exit code 0/1/2/3） - コンパイラモード説明（harness vs crate） - デバッグセクション拡張 - "1コマンドで再現" 可能な状態を確立 Phase 131-2 完了: ConsoleBox 問題調査 - VM の 3重登録経路を特定（BoxFactoryRegistry/UnifiedRegistry/Builtin） - LLVM backend は Phase 133 で解決済み - 3つのドキュメント作成: - phase131-2-consolebox-investigation.md（詳細調査） - phase131-2-summary.md（エグゼクティブサマリ） - phase131-2-box-resolution-map.md（Box 解決マップ） Phase 86-90 完了: Loop frontends 要約 - phase86-90-loop-frontends-summary.md 追加 - Pattern4/ContinueReturn/ParseStringComposite の経緯を1枚に集約 - INDEX から導線追加 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 05:24:31 +09:00
- Phase 86–90（Loop frontends）まとめ（1枚）:
- `docs/development/current/main/phase86-90-loop-frontends-summary.md`
docs(joinir): Phase 86 到達点 - Carrier init builder + Error tags SSOT Phase 74-86 成果を SSOT docs に反映: - 10-Now.md: Phase 86 achievements summary - INDEX: carrier_init_builder, error_tags modules documented - architecture-overview: SSOT module references added Impact: 987/987 tests, +13 unit tests, 2 new SSOT modules Modules: carrier_init_builder.rs, error_tags.rs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-13 22:37:56 +09:00
docs(phase131): LLVM SSOT強化 + ConsoleBox調査完了 + Phase86-90要約 Phase 131-1 完了: LLVM exe line SSOT 強化 - phase87-selfhost-llvm-exe-line.md に 4セクション追加（+300行） - 環境変数リファレンス（14変数） - 成功/失敗基準（exit code 0/1/2/3） - コンパイラモード説明（harness vs crate） - デバッグセクション拡張 - "1コマンドで再現" 可能な状態を確立 Phase 131-2 完了: ConsoleBox 問題調査 - VM の 3重登録経路を特定（BoxFactoryRegistry/UnifiedRegistry/Builtin） - LLVM backend は Phase 133 で解決済み - 3つのドキュメント作成: - phase131-2-consolebox-investigation.md（詳細調査） - phase131-2-summary.md（エグゼクティブサマリ） - phase131-2-box-resolution-map.md（Box 解決マップ） Phase 86-90 完了: Loop frontends 要約 - phase86-90-loop-frontends-summary.md 追加 - Pattern4/ContinueReturn/ParseStringComposite の経緯を1枚に集約 - INDEX から導線追加 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 05:24:31 +09:00
### Phase 86–90: Loop frontends（要約）
docs(joinir): Phase 86 到達点 - Carrier init builder + Error tags SSOT Phase 74-86 成果を SSOT docs に反映: - 10-Now.md: Phase 86 achievements summary - INDEX: carrier_init_builder, error_tags modules documented - architecture-overview: SSOT module references added Impact: 987/987 tests, +13 unit tests, 2 new SSOT modules Modules: carrier_init_builder.rs, error_tags.rs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-13 22:37:56 +09:00
docs(phase131): LLVM SSOT強化 + ConsoleBox調査完了 + Phase86-90要約 Phase 131-1 完了: LLVM exe line SSOT 強化 - phase87-selfhost-llvm-exe-line.md に 4セクション追加（+300行） - 環境変数リファレンス（14変数） - 成功/失敗基準（exit code 0/1/2/3） - コンパイラモード説明（harness vs crate） - デバッグセクション拡張 - "1コマンドで再現" 可能な状態を確立 Phase 131-2 完了: ConsoleBox 問題調査 - VM の 3重登録経路を特定（BoxFactoryRegistry/UnifiedRegistry/Builtin） - LLVM backend は Phase 133 で解決済み - 3つのドキュメント作成: - phase131-2-consolebox-investigation.md（詳細調査） - phase131-2-summary.md（エグゼクティブサマリ） - phase131-2-box-resolution-map.md（Box 解決マップ） Phase 86-90 完了: Loop frontends 要約 - phase86-90-loop-frontends-summary.md 追加 - Pattern4/ContinueReturn/ParseStringComposite の経緯を1枚に集約 - INDEX から導線追加 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 05:24:31 +09:00
- Phase 86–90 は “dev-only fixtures + shape guard + fail-fast” で段階的に固定済み。
- 具体の fixture / shape / 未検証は `docs/development/current/main/phase86-90-loop-frontends-summary.md` を SSOT とする。
feat(joinir): Phase 89 P0 - Continue + Early Return pattern detector ## Pattern4 Detector 締め - is_pattern4_continue_minimal() を厳しく - Select 必須 + conditional Jump exactly 1 - loop 内 return を P4 と誤認しない ## 新パターン箱 - LoopPattern::ContinueReturn enum 追加 - has_return_in_loop_body() helper 追加 - Fail-Fast: UnimplementedPattern error ## Normalized-dev 統合 - NormalizedDevShape::PatternContinueReturnMinimal - detector: Select + conditional Jumps >= 2 - canonical には入れない（dev-only） ## Documentation - 10-Now.md, CURRENT_TASK.md 更新 Impact: - 987 lib tests PASS - 60 normalized_dev tests PASS - Pattern4 誤爆防止 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 00:59:58 +09:00
docs(joinir): Phase 80 Tasks 80-0/80-A - Status verification + design doc Task 80-0: Current status verification - ✅ 970/970 lib tests PASS (production stable) - ✅ Core VM smoke tests PASS (json_pp_vm) - ❌ Phase 79 E2E tests broken (AST API mismatch, out-of-scope) - ❌ Pre-existing json_lint_vm failure (Pattern2 verifier, out-of-scope) - **Conclusion**: Phase 80 has ZERO blockers Task 80-A: SSOT design doc created - New: docs/development/current/main/phase80-bindingid-p3p4-plan.md (336 lines) - Pattern3/4 BindingId wiring strategy - Implementation order: 80-B (P3) → 80-C (P4) → 80-D (E2E) - Code examples and success metrics - Fallback detection mechanism (existing log tags) Design principles (consistent with Phase 74-79): - Dev-only code (feature-gated) - Dual-path maintained (BindingId priority + name fallback) - Structural detection only (NO by-name branching) - Fail-Fast error handling - Zero production impact Updated docs: - 01-JoinIR-Selfhost-INDEX.md: Phase 79 Activation status - 10-Now.md: Phase 80 tasks 80-0/80-A complete - 20-Decisions.md: BindingId migration complete status - joinir-architecture-overview.md: Phase 79/80 sections Next: Task 80-B (Pattern3 BindingId registration)
2025-12-13 17:26:15 +09:00
### Scope / BindingId（dev-only の段階移行ライン）
- MIR builder 側で lexical scope / shadowing を実在化し、言語仕様の “local はブロック境界で分離” を SSOT に揃えた。
- JoinIR lowering 側は name-based から BindingId-based へ段階移行中：
- `ScopeManager.lookup_with_binding()` / `ConditionEnv.binding_id_map` を導入し、shadowing を壊さずに解決できる足場を作った。
- promoted carriers（DigitPos/Trim）については `BindingId(original) → BindingId(promoted) → ValueId(join)` の鎖を dev-only で整備中。
docs(joinir): Phase 86 SSOT 追記完了 + Phase 88 準備 Phase 86 SSOT 追記（P0 完了）: - 10-Now.md: carrier_init_builder / error_tags 確立を追記 - CURRENT_TASK.md: P0→P1 繰り上げ、Done 節追加 Phase 88 準備: - nyash_kernel/lib.rs: AOT 実行器で Ring0Context 初期化 - nyash.toml: プラグインパス正規化（plugins/...） - auto_detect.conf: integration タイムアウト 120秒に延長 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 00:05:16 +09:00
- Phase 86 で `carrier_init_builder` / `error_tags` を SSOT 化し、段階移行ラインの基盤（ValueId 生成とエラー語彙）が確立した。
- これにより、BindingId dual-path の拡張・統合時に「生成」と「表示」の責務が混ざらない構造が固定された。
docs(joinir): link Phase 81 ExitLine contract SSOT Phase 81 完了を受けて docs リンク追加: - 01-JoinIR-Selfhost-INDEX.md: Phase 81 entry - 10-Now.md: Phase 81 status update - joinir-architecture-overview.md: Phase 81 ExitLine contract verification section Phase 74-81 complete: BindingId migration + ExitLine contract verified
2025-12-13 18:46:07 +09:00
- Phase 81 で Pattern2（DigitPos/Trim）の ExitLine 契約（ConditionOnly を exit PHI から除外、LoopState のみを reconnect）を E2E で固定した。
docs(joinir): Phase 80 Tasks 80-0/80-A - Status verification + design doc Task 80-0: Current status verification - ✅ 970/970 lib tests PASS (production stable) - ✅ Core VM smoke tests PASS (json_pp_vm) - ❌ Phase 79 E2E tests broken (AST API mismatch, out-of-scope) - ❌ Pre-existing json_lint_vm failure (Pattern2 verifier, out-of-scope) - **Conclusion**: Phase 80 has ZERO blockers Task 80-A: SSOT design doc created - New: docs/development/current/main/phase80-bindingid-p3p4-plan.md (336 lines) - Pattern3/4 BindingId wiring strategy - Implementation order: 80-B (P3) → 80-C (P4) → 80-D (E2E) - Code examples and success metrics - Fallback detection mechanism (existing log tags) Design principles (consistent with Phase 74-79): - Dev-only code (feature-gated) - Dual-path maintained (BindingId priority + name fallback) - Structural detection only (NO by-name branching) - Fail-Fast error handling - Zero production impact Updated docs: - 01-JoinIR-Selfhost-INDEX.md: Phase 79 Activation status - 10-Now.md: Phase 80 tasks 80-0/80-A complete - 20-Decisions.md: BindingId migration complete status - joinir-architecture-overview.md: Phase 79/80 sections Next: Task 80-B (Pattern3 BindingId registration)
2025-12-13 17:26:15 +09:00
- 参照:
- `docs/development/current/main/phase73-scope-manager-design.md`
- `docs/development/current/main/phase78-bindingid-promoted-carriers.md`
- `docs/development/current/main/phase80-bindingid-p3p4-plan.md`
docs(joinir): link Phase 81 ExitLine contract SSOT Phase 81 完了を受けて docs リンク追加: - 01-JoinIR-Selfhost-INDEX.md: Phase 81 entry - 10-Now.md: Phase 81 status update - joinir-architecture-overview.md: Phase 81 ExitLine contract verification section Phase 74-81 complete: BindingId migration + ExitLine contract verified
2025-12-13 18:46:07 +09:00
- `docs/development/current/main/phase81-pattern2-exitline-contract.md`
docs(joinir): Phase 78-85 Boxification Feedback Report Comprehensive analysis of boxification patterns effectiveness. Key Findings: - Overall: Exceptional success ⭐⭐⭐⭐⭐ (24/25 avg rating) - Net code reduction: -1,388 lines (Phase 78-79: -530L, Phase 85: -858L) - 4 new Boxes: PromotedBindingRecorder, Detector/Recorder, BindingMapProvider, DebugOutputBox - 28 new unit tests, 974/974 PASS maintained Box Ratings (out of 25): - PromotedBindingRecorder: 24/25 (67% wiring reduction) - Detector/Recorder: 24/25 (60% code reduction, SRP) - BindingMapProvider: 23/25 (80% cfg reduction) - DebugOutputBox: 21/25 (centralized debug output) Phase 86 Recommendations: - GO: Carrier Initialization Builder (HIGH, 2-3h, -100L) - GO: Remaining DebugOutputBox Migration (QUICK, 30m) - GO: Error Message Centralization (LOW, 1-2h) - NO-GO: Detector/Promoter Pipeline (over-abstraction risk) - NO-GO: ScopeManager Lookup Variants (premature) Lessons Learned: - Single Responsibility principle validated - Testability-first approach successful - Low migration cost (1-2h per phase) - Zero production risk (all dev-only/backward-compatible) Report: phase78-85-boxification-feedback.md (~1,200 lines) Updated: INDEX, Now, architecture-overview (Phase 85 links)
2025-12-13 21:32:35 +09:00
- `docs/development/current/main/phase78-85-boxification-feedback.md`
docs(joinir): Phase 80 Tasks 80-0/80-A - Status verification + design doc Task 80-0: Current status verification - ✅ 970/970 lib tests PASS (production stable) - ✅ Core VM smoke tests PASS (json_pp_vm) - ❌ Phase 79 E2E tests broken (AST API mismatch, out-of-scope) - ❌ Pre-existing json_lint_vm failure (Pattern2 verifier, out-of-scope) - **Conclusion**: Phase 80 has ZERO blockers Task 80-A: SSOT design doc created - New: docs/development/current/main/phase80-bindingid-p3p4-plan.md (336 lines) - Pattern3/4 BindingId wiring strategy - Implementation order: 80-B (P3) → 80-C (P4) → 80-D (E2E) - Code examples and success metrics - Fallback detection mechanism (existing log tags) Design principles (consistent with Phase 74-79): - Dev-only code (feature-gated) - Dual-path maintained (BindingId priority + name fallback) - Structural detection only (NO by-name branching) - Fail-Fast error handling - Zero production impact Updated docs: - 01-JoinIR-Selfhost-INDEX.md: Phase 79 Activation status - 10-Now.md: Phase 80 tasks 80-0/80-A complete - 20-Decisions.md: BindingId migration complete status - joinir-architecture-overview.md: Phase 79/80 sections Next: Task 80-B (Pattern3 BindingId registration)
2025-12-13 17:26:15 +09:00
feat(joinir): Phase 171-fix ConditionEnv/ConditionBinding architecture Proper HOST↔JoinIR ValueId separation for condition variables: - Add ConditionEnv struct (name → JoinIR-local ValueId mapping) - Add ConditionBinding struct (HOST/JoinIR ValueId pairs) - Modify condition_to_joinir to use ConditionEnv instead of builder.variable_map - Update Pattern2 lowerer to build ConditionEnv and ConditionBindings - Extend JoinInlineBoundary with condition_bindings field - Update BoundaryInjector to inject Copy instructions for condition variables This fixes the undefined ValueId errors where HOST ValueIds were being used directly in JoinIR instructions. Programs now execute (RC: 0), though loop variable exit values still need Phase 172 work. Key invariants established: 1. JoinIR uses ONLY JoinIR-local ValueIds 2. HOST↔JoinIR bridging is ONLY through JoinInlineBoundary 3. condition_to_joinir NEVER accesses builder.variable_map 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-07 01:45:03 +09:00
### JsonParser / Selfhost depth‑2 ライン
- `selfhost_build.sh --json` で Program JSON v0 emit は安定。
`.hako` 側から env 経由で JSON を読む最小ループ（`program_read_min.hako`）は動作確認済み。
- JsonParserBox / BundleResolver のループ 21 本のうち：
- 18 本は Pattern1–4 で JoinIR 対応済み（Phase 162–165）。
- `_trim` を含む一部の複合ループは、ValueId 境界や Box 登録など残課題あり。
- BoolExprLowerer / condition_to_joinir で OR/AND/NOT 付き条件式の lowering は実装完了（Phase 168–169）。
- 残課題（JsonParser/selfhost depth‑2）：
- JoinIR→MIR ValueId boundary の完全一般化（条件用 ValueId を含める）
- JsonParserBox の using / Box 登録（Rust VM 側での認識）
- Program JSON v0 を JsonParserBox 経由でフル解析する line の仕上げ
### Ring0 / Runtime / CoreServices ライン
- Ring0Context + Ring0Registry で OS API 抽象化レイヤ完成：
- MemApi / IoApi / TimeApi / LogApi / FsApi / ThreadApi
- RuntimeProfile(Default / NoFs) で条件付き必須を制御。
- CoreServices（ring1‑core）として次を実装済み：
- StringService / IntegerService / BoolService
- ArrayService / MapService / ConsoleService
- PluginHost 統合 + UnifiedBoxRegistry からの自動初期化
- FileBox / FileHandleBox ライン：
- Ring0FsFileIo 経由で read / write / append / metadata 完全対応
- Default プロファイルでは必須、NoFs プロファイルでは disabled。
- Logging ライン：
- ConsoleService（user‑facing）
- Ring0.log（internal/dev）
- println!（test 専用）
の 3 層が `logging_policy.md` で整理済み。JoinIR/Loop trace も同ドキュメントに集約。
docs(phase131): LLVM SSOT強化 + ConsoleBox調査完了 + Phase86-90要約 Phase 131-1 完了: LLVM exe line SSOT 強化 - phase87-selfhost-llvm-exe-line.md に 4セクション追加（+300行） - 環境変数リファレンス（14変数） - 成功/失敗基準（exit code 0/1/2/3） - コンパイラモード説明（harness vs crate） - デバッグセクション拡張 - "1コマンドで再現" 可能な状態を確立 Phase 131-2 完了: ConsoleBox 問題調査 - VM の 3重登録経路を特定（BoxFactoryRegistry/UnifiedRegistry/Builtin） - LLVM backend は Phase 133 で解決済み - 3つのドキュメント作成: - phase131-2-consolebox-investigation.md（詳細調査） - phase131-2-summary.md（エグゼクティブサマリ） - phase131-2-box-resolution-map.md（Box 解決マップ） Phase 86-90 完了: Loop frontends 要約 - phase86-90-loop-frontends-summary.md 追加 - Pattern4/ContinueReturn/ParseStringComposite の経緯を1枚に集約 - INDEX から導線追加 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 05:24:31 +09:00
- VM backend の Box 解決（UnifiedBoxRegistry / BoxFactoryRegistry）の経路図:
- `docs/development/current/main/phase131-2-box-resolution-map.md`
fix(llvm): Phase 131-10 - Smart console.log routing（Segfault修正） ## 問題 - Integer値をi8*ポインタに変換 → Segfault（Exit 139） ## 解決策 - String literal → nyash.console.log(i8*) - Integer/Handle → nyash.console.log_handle(i64) ## 結果 - Case B (loop_min_while): LLVM outputs `0,1,2` ✅ - VM/LLVM完全パリティ達成 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-14 09:19:00 +09:00
- LLVM（Python llvmlite）lowering の棚卸し（Phase 131-3..10）:
docs(phase131): Phase 131-3 完了 - LLVM lowering 棚卸し（3ケース） Phase 131-3 完了: MIR→LLVM lowering 棚卸し テスト結果マトリックス: - Case A (phase87_llvm_exe_min.hako): ✅ PASS (baseline) - Case B (loop_min_while.hako): ❌ TAG-EMIT (PHI after terminator) - Case B2 (print(42) simple): ✅ PASS (BoxCall works) - Case C (llvm_stage3_loop_only.hako): ❌ TAG-EMIT (JoinIR pattern gap) Critical Bugs: 1. Bug #1: PHI After Terminator (Case B) - 原因: function_lower.py が terminator を PHI より先に emit - 修正: 4-pass block emission (2-3h) 2. Bug #2: JoinIR Pattern Gap (Case C) - 原因: loop(true) { break } パターンが JoinIR 未対応 - 修正: Pattern 5 設計・実装 (3-4h) Next Actions: - P1 (推奨): PHI ordering 修正 → 80% のループを有効化 - P2: JoinIR Pattern 5 → infinite loop 対応 ドキュメント: - phase131-3-llvm-lowering-inventory.md: 詳細棚卸し結果 - phase87-selfhost-llvm-exe-line.md: LLVM IR parsing error 追記 - CURRENT_TASK.md: phase131-3 参照追加 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-14 05:55:21 +09:00
- `docs/development/current/main/phase131-3-llvm-lowering-inventory.md`
feat(llvm): Phase 132 - Pattern 1 exit value parity fix + Box-First refactoring ## Phase 132: Exit PHI Value Parity Fix ### Problem Pattern 1 (Simple While) returned 0 instead of final loop variable value (3) - VM: RC: 3 ✅ (correct) - LLVM: Result: 0 ❌ (wrong) ### Root Cause (Two Layers) 1. **JoinIR/Boundary**: Missing exit_bindings → ExitLineReconnector not firing 2. **LLVM Python**: block_end_values snapshot dropping PHI values ### Fix **JoinIR** (simple_while_minimal.rs): - Jump(k_exit, [i_param]) passes exit value **Boundary** (pattern1_minimal.rs): - Added LoopExitBinding with carrier_name="i", role=LoopState - Enables ExitLineReconnector to update variable_map **LLVM** (block_lower.py): - Use predeclared_ret_phis for reliable PHI filtering - Protect builder.vmap PHIs from overwrites (SSOT principle) ### Result - ✅ VM: RC: 3 - ✅ LLVM: Result: 3 - ✅ VM/LLVM parity achieved ## Phase 132-Post: Box-First Refactoring ### Rust Side **JoinModule::require_function()** (mod.rs): - Encapsulate function search logic - 10 lines → 1 line (90% reduction) - Reusable for Pattern 2-5 ### Python Side **PhiManager Box** (phi_manager.py - new): - Centralized PHI lifecycle management - 47 lines → 8 lines (83% reduction) - SSOT: builder.vmap owns PHIs - Fail-Fast: No silent overwrites **Integration**: - LLVMBuilder: Added phi_manager - block_lower.py: Delegated to PhiManager - tagging.py: Register PHIs with manager ### Documentation **New Files**: - docs/development/architecture/exit-phi-design.md - docs/development/current/main/investigations/phase132-llvm-exit-phi-wrong-result.md - docs/development/current/main/phases/phase-132/ **Updated**: - docs/development/current/main/10-Now.md - docs/development/current/main/phase131-3-llvm-lowering-inventory.md ### Design Principles - Box-First: Logic encapsulated in classes/methods - SSOT: Single Source of Truth (builder.vmap for PHIs) - Fail-Fast: Early explicit failures, no fallbacks - Separation of Concerns: 3-layer architecture 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-15 03:17:31 +09:00
- 状態: Case B（Pattern1/loop_min_while）は EMIT/LINK/RUN まで復旧済み。Phase 132 で `return i` の VM/LLVM parity を固定。
- Case C は別途 “Case C docs” を SSOT にして追跡する（状況は更新されるので、この箇所では断定しない）
docs(phase131): Case C 調査完了 - InfiniteEarlyExit パターン追加方針 ## 根本原因解明 - loop(true) が Pattern4 に誤ルーティング - Pattern4 は BinaryOp 比較を期待、boolean literal で失敗 ## 解決方針 - 新パターン InfiniteEarlyExit 追加（Pattern 2 拡張ではなく） - classify() の優先度修正 - Shape guard で最小受理（break+continue 各1箇所） ## 作成ドキュメント - case-c-infinite-loop-analysis.md (13KB詳細分析) - phase131-11-case-c-summary.md (4KBサマリー) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-14 09:47:23 +09:00
- Case C の調査と実装計画:
- `docs/development/current/main/phase131-11-case-c-summary.md`
- `docs/development/current/main/case-c-infinite-loop-analysis.md`
feat(joinir): Phase 171-fix ConditionEnv/ConditionBinding architecture Proper HOST↔JoinIR ValueId separation for condition variables: - Add ConditionEnv struct (name → JoinIR-local ValueId mapping) - Add ConditionBinding struct (HOST/JoinIR ValueId pairs) - Modify condition_to_joinir to use ConditionEnv instead of builder.variable_map - Update Pattern2 lowerer to build ConditionEnv and ConditionBindings - Extend JoinInlineBoundary with condition_bindings field - Update BoundaryInjector to inject Copy instructions for condition variables This fixes the undefined ValueId errors where HOST ValueIds were being used directly in JoinIR instructions. Programs now execute (RC: 0), though loop variable exit values still need Phase 172 work. Key invariants established: 1. JoinIR uses ONLY JoinIR-local ValueIds 2. HOST↔JoinIR bridging is ONLY through JoinInlineBoundary 3. condition_to_joinir NEVER accesses builder.variable_map 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-07 01:45:03 +09:00
---
## 2025‑09‑08：旧スナップショット（参考）
docs(current_task): add structured tasks under docs/current_task/{main,llvm,self_current_task} and unignore path
2025-09-08 11:35:30 +09:00
- LLVM 側 P0 完了（BitOps/Array/Echo/Map 緑）。VInvoke(by‑name/by‑id vector) は戻り値マッピングの暫定課題を確認中（Decisions 参照）。
- selfhosting-dev の作業を main に順次取り込み。VM/MIR 基盤は main で先に整える方針。
feat(joinir): Phase 171-fix ConditionEnv/ConditionBinding architecture Proper HOST↔JoinIR ValueId separation for condition variables: - Add ConditionEnv struct (name → JoinIR-local ValueId mapping) - Add ConditionBinding struct (HOST/JoinIR ValueId pairs) - Modify condition_to_joinir to use ConditionEnv instead of builder.variable_map - Update Pattern2 lowerer to build ConditionEnv and ConditionBindings - Extend JoinInlineBoundary with condition_bindings field - Update BoundaryInjector to inject Copy instructions for condition variables This fixes the undefined ValueId errors where HOST ValueIds were being used directly in JoinIR instructions. Programs now execute (RC: 0), though loop variable exit values still need Phase 172 work. Key invariants established: 1. JoinIR uses ONLY JoinIR-local ValueIds 2. HOST↔JoinIR bridging is ONLY through JoinInlineBoundary 3. condition_to_joinir NEVER accesses builder.variable_map 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-07 01:45:03 +09:00
直近タスク（当時）
docs(current_task): add structured tasks under docs/current_task/{main,llvm,self_current_task} and unignore path
2025-09-08 11:35:30 +09:00
1) continue/break の lowering（Builder 修正のみで表現）
- ループ文脈スタック {head, exit} を導入。
- continue に遭遇 → head（または latch）へ br を emit し終端。
- break に遭遇 → exit へ br を emit し終端。
- post‑terminated 後に emit しない制御を徹底。
2) ループ CFG の厳密化
- 単一 exit ブロックの徹底。
- Phi はヘッダでキャリー変数を合流（SSA/支配関係が崩れない形）。
3) 検証とスモーク
- Verifier 緑（dominance/SSA）。
- VM のループ代表（単純/ネスト/早期継続・脱出）。
- LLVM/Cranelift EXE に綺麗に降りる（br/phi ベースで問題なし）。
代表コマンド（例）
- ビルド: `cargo build --release`
- LLVM smoke: `LLVM_SYS_180_PREFIX=$(llvm-config-18 --prefix) NYASH_LLVM_BITOPS_SMOKE=1 ./tools/llvm_smoke.sh release`
- VInvoke 調査: `NYASH_LLVM_VINVOKE_TRACE=1 NYASH_LLVM_VINVOKE_SMOKE=1 ./tools/llvm_smoke.sh release`
Reference in New Issue Copy Permalink