Phase 276 P0 post-Phase 275 robustness improvements: 1. Debug cleanup (wiring.py L100-103): - Remove traceback.format_stack() output - Cleaner debug logs after Phase 275 completion 2. box_from_f64 usage investigation: - Confirmed ZERO usage (Rust/Python/MIR) - Ready for deletion (Phase 275 unboxed double SSOT) - crates/nyash_kernel/src/lib.rs L244-252, L971-982 3. Type resolution SSOT (⭐ most important): - New file: src/llvm_py/phi_wiring/type_helper.py (72 lines) - Unified 3 duplicate logic sites: * tagging.py: inst.get("dst_type") → type_helper.get_phi_dst_type() * llvm_builder.py: 9 lines → 2 lines (-7) * wiring.py: 18 lines → 5 lines (-13) - Priority: MIR JSON dst_type > resolver.value_types - Benefits: SSOT principle, bug prevention, easy extension 4. Type mismatch warning enhancement (wiring.py L63-79): - CRITICAL warning for predeclared PHI type mismatch - PhiManager.invalidate_phi() notification - Early bug detection with ⚠️ marker Effects: - Type resolution logic: 3 sites → 1 SSOT (type_helper.py) - Code reduction: -20 lines duplicate logic - Robustness: SSOT principle, CRITICAL warnings, Fail-Fast - Debuggability: cleaner logs, prominent type mismatch alerts Testing: - LLVM harness: exit=3 verified (/tmp/test_p275_debug2.hako) - NYASH_PHI_TYPE_DEBUG=1: correct type resolution confirmed Docs: - Phase 276 P0 completion: docs/.../phase-276/P0-COMPLETION.md - 10-Now.md: Phase 276 P0 ✅, Phase 275 P0 completed section Next steps (Phase 277 P0 recommended): - Delete box_from_f64 (nyash.box.from_f64, nyash.float.box_from_f64) - Adopt dst_type_to_llvm_type() helper 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Phase ドキュメント
このフォルダは、実装フェーズ(Phase 131, Phase 33 等)ごとの詳細記録を保管します。
現在の Phase
- Phase 139(DONE): post-if
post_kの return lowering をReturnValueLowererBoxに統一(出口 SSOT 完成) - Phase 140(DONE):
NormalizedExprLowererBox初版(pure expression のみ) - Phase 141 P0(DONE): impure 拡張点(contract)を SSOT 化(Call/MethodCall はまだ out-of-scope)
- Phase 141 P1(DONE): “既知 intrinsic だけ” を許可して段階投入(length0)
- Phase 141 P1.5(DONE): known intrinsic registry + available_inputs 3-source merge + diagnostics
- Phase 141 P2+(planned): Call/MethodCall 対応(effects + typing の段階投入)
- Phase 142-loopstmt P0(DONE): 正規化単位を statement(loop 1個)へ寄せる(パターン爆発を止める)
- Phase 142-loopstmt P1(DONE): LLVM EXE smoke(同 fixture)を追加
- Phase 143-loopvocab(planned): StepTree の語彙拡張(loop 内 if/break/continue を「語彙追加」で吸収)
- Phase 91–92: Selfhost depth‑2 coverage(P5b escape recognition → lowering)
- Phase 94–100: P5b escape E2E / Trim policy / pinned + accumulator(VM/LLVM EXE parity)
- Phase 102: real-app read_quoted loop regression(VM + LLVM EXE)
- Phase 103: if-only regression baseline(VM + LLVM EXE / plan)
- Phase 113: if-only partial assign parity(片側代入の保持 merge)
- Phase 107–109: real-app depth-scan / policy router SSOT / error hint SSOT
- Phase 110–112: ControlTree / StepTree(構造SSOT, dev-only)※設計SSOTは
../design/control-tree.md
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 (根本原因分析)
参照方法
- 現在の Phase を知りたい → ../10-Now.md
- 該当 Phase を詳しく知りたい → フォルダを開く
- 設計背景を知りたい → ../design/
- 調査ログを見たい → ../investigations/
Phase 命名規則
- ファイル名:
phase-<N>-<title>/(例:phase-131/) - 文書名:
<N>-<NN>-<topic>.md(例:131-11-case-c-summary.md)- Phase 番号で自然にソート可能
- 同一 Phase 内で段階的に追跡可能
作成ルール(SSOT)
詳しくは ../DOCS_LAYOUT.md を参照。
- ✅ 置き場所:
phases/phase-<N>/配下のみ - ✅ 内容: Phase の実装記録・進捗・チェックリスト・検証結果
- ❌ 避けるべき: 複数 Phase で参照される設計・アーキテクチャ(→ design/ へ)
最終更新: 2025-12-19