447d4ea246
## 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>
46 lines
1.6 KiB
Markdown
46 lines
1.6 KiB
Markdown
# Phase ドキュメント
|
||
|
||
このフォルダは、実装フェーズ（Phase 131, Phase 33 等）ごとの詳細記録を保管します。
|
||
|
||
## 現在の Phase
|
||
|
||
- **Phase 132**: Exit Values Parity (VM == LLVM)
|
||
- **Phase 131**: LLVM Lowering & InfiniteEarlyExit パターン実装 🚀
|
||
- **Phase 33**: Box Theory Modularization
|
||
|
||
## Phase フォルダ構成（推奨）
|
||
|
||
```
|
||
phases/phase-131/
|
||
├── README.md (Phase 全体概要)
|
||
├── 131-03-llvm-lowering-inventory.md (LLVM 部分のテスト・検証)
|
||
├── 131-11-case-c-summary.md (Case C 実装サマリー)
|
||
└── phase131-11-case-c-root-cause-analysis.md (根本原因分析)
|
||
```
|
||
|
||
## 参照方法
|
||
|
||
1. **現在の Phase を知りたい** → [../10-Now.md](../10-Now.md)
|
||
2. **該当 Phase を詳しく知りたい** → フォルダを開く
|
||
3. **設計背景を知りたい** → [../design/](../design/README.md)
|
||
4. **調査ログを見たい** → [../investigations/](../investigations/README.md)
|
||
|
||
## Phase 命名規則
|
||
|
||
- **ファイル名**: `phase-<N>-<title>/` (例: `phase-131/`)
|
||
- **文書名**: `<N>-<NN>-<topic>.md` (例: `131-11-case-c-summary.md`)
|
||
- Phase 番号で自然にソート可能
|
||
- 同一 Phase 内で段階的に追跡可能
|
||
|
||
## 作成ルール（SSOT）
|
||
|
||
詳しくは [../DOCS_LAYOUT.md](../DOCS_LAYOUT.md) を参照。
|
||
|
||
- ✅ **置き場所**: `phases/phase-<N>/` 配下のみ
|
||
- ✅ **内容**: Phase の実装記録・進捗・チェックリスト・検証結果
|
||
- ❌ **避けるべき**: 複数 Phase で参照される設計・アーキテクチャ（→ design/ へ）
|
||
|
||
---
|
||
|
||
**最終更新**: 2025-12-15
|