Commit Graph

77 Commits

Author SHA1 Message Date
4120ab65c9 fix(selfhost): StringBox.get() エラー修正でセルフホスト復活!
StageBDriverBox.compile() と main() 内の2箇所に防御チェック追加:
- methods.get(mi) が null の場合スキップ
- methods.get(mi) が StringBox の場合スキップ (MapBox のみ処理)

これにより "Unknown method 'get' on StringBox" エラーが解消され、
.hako セルフホストコンパイラが再び動作するようになった。

テスト確認:
NYASH_USE_NY_COMPILER=1 ./target/release/hakorune test.hako
→ "Hello from selfhost!" RC: 0 

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-25 09:18:43 +09:00
c479e5f527 fix(dx): Quick Win 1-3 for better error messages and API simplification
Quick Win 1: Show available boxes on "Unknown Box type" error
- vm.rs, vm_fallback.rs: Display sorted list of available user-defined boxes
- Before: "Unknown Box type: Foo"
- After:  "Unknown Box type: Foo. Available: Bar, Baz, Main"

Quick Win 2: Show stderr on child process timeout
- child.rs, selfhost_exe.rs: Capture and display stderr (up to 500 chars)
- Helps diagnose what went wrong in selfhost compiler child process

Quick Win 3: Simplify Stage-B compiler API (SSOT)
- compiler_stageb.hako: Add StageBDriverBox.compile() as single entry point
- compiler_stageb.hako: Remove StageBMain compatibility wrapper
- compiler.hako: Change from `using ... as StageBMain` to direct import
- compiler.hako: Call StageBDriverBox.compile() directly

Also includes child_env.rs NYASH_MODULES env var for module mapping.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-25 08:44:31 +09:00
844e53d96c fix(parser): Part 5 - eliminate infinite loops in parse_string2 and scan_with_quote
Problem: Nested escape sequence processing in string parsing functions caused
infinite loops due to missing continue statements, allowing fallthrough to the
else block which corrupted the position counter.

Fixed functions:
- parser_expr_box.hako::parse_string2 (lines 22-83)
- parser_string_scan_box.hako::scan_with_quote (lines 11-101)

Changes:
- Flattened nested 'else { if ... }' chains to flat 'if' statements
- Added explicit 'continue' after each escape sequence processing
- Prevents fallthrough to position increment code

Verification:
 NYASH_USE_STAGE1_CLI=1 STAGE1_EMIT_PROGRAM_JSON=1 HAKO_VM_MAX_STEPS=2000000
   apps/tests/minimal_ssa_skip_ws.hako
 No budget exceeded
 Program JSON v0 output to stdout
 Exit code: 0

MirBuilder-friendly pattern applied consistently with Parts 1-4.
Stage-1 CLI infinite loop elimination COMPLETE!
2025-11-25 00:16:29 +09:00
b21ee3c854 fix(parser): Part 3-4 - Fix remaining infinite loops in parser subsystems
Part 3 (included):
- parser_box.hako: Fix semicolon consumption loop (lines 401-421)

Part 4 (systematic fix of 7 files):
- parser_number_scan_box.hako: Fix scan_int digit scanning loop
- parser_literal_box.hako: Fix parse_map and parse_array loops (2 loops)
- parser_peek_box.hako: Fix peek expression arms parsing loop
- parser_control_box.hako: Fix parse_block and semicolon loops (2 loops)
- parser_exception_box.hako: Fix try/catch clauses loop
- parser_stmt_box.hako: Fix using statement namespace parsing loop

Root cause: MirBuilder bug with loop(flag == 0/1) + nested if-else
- Generated broken MIR with PHI self-references
- Caused infinite loops in VM execution

Solution: Convert all problematic loops to MirBuilder-friendly pattern:
  loop(true) { if condition { continue } else { break } }

Test results:  Stage-1 CLI now completes without timeout
- Exit code: 0
- MIR dump created successfully
- parse_program2 ws_init: 1 iteration (was infinite)

Total loops fixed across all parts: 18 loops in 11 files

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-24 21:34:22 +09:00
54b9597af6 fix(parser): Stage-1 CLI infinite loop - fix ParserExprBox and ParserIdentScanBox (Part 2/3)
**Problem**: Multiple infinite loops in parser expression handling
- ParserIdentScanBox.scan_ident: bb985
- ParserExprBox.parse_factor2: bb1662 (2 loops)
- ParserExprBox.parse_term2: bb1704
- ParserExprBox.parse_sum2
- ParserExprBox.parse_expr2
- ParserExprBox.parse_args2

**Root Cause**: Same `loop(cont == 1)` + nested if-else pattern as Part 1
- MirBuilder generates PHI self-references
- Loop exits jump to wrong blocks

**Solution**: MirBuilder-friendly explicit continue/break pattern
```hako
// BAD:
loop(cont == 1) {
  if condition { action } else { cont = 0 }
}

// GOOD:
loop(true) {
  if condition { action; continue }
  break
}
```

**Files Modified**:
- lang/src/compiler/parser/scan/parser_ident_scan_box.hako: scan_ident explicit continue
- lang/src/compiler/parser/expr/parser_expr_box.hako: 6 loops fixed
  - parse_factor2: 2 method chaining loops (new/identifier)
  - parse_term2: */ operators
  - parse_sum2: +- operators
  - parse_expr2: &&|| operators
  - parse_args2: argument list parsing

**Progress**: 9 total loop patterns fixed (Part 1: 3, Part 2: 6)

**Remaining**: parse_program2 still has infinite loop at different location (bb2816 vs original bb2854) - investigating in Part 3

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-24 18:34:43 +09:00
c6c5653ae0 fix(parser): Stage-1 CLI infinite loop - MirBuilder-friendly refactoring (Part 1/3)
**Problem**: Stage-1 CLI hits VM step budget (infinite loops) in multiple functions
- ParserBox.parse_program2: bb2853→bb2854 loop
- StringHelpers.skip_ws: bb488→bb491 loop

**Root Cause**: MirBuilder bug with `loop(cont==1)` + nested `if-else` pattern
- PHI instructions with self-references
- Loop exit blocks jumping back to header instead of continuation

**Solution**: Refactor to MirBuilder-friendly pattern
```hako
// Before (causes infinite loop):
loop(cont == 1) {
  if guard > max { return j } else { guard++ }
  if condition { action } else { cont = 0 }
}

// After (MirBuilder-friendly):
loop(j < n) {
  if condition { j++; continue }
  break
}
```

**Changes**:
1. parser_box.hako: parse_program2 main loop refactored
   - 7 sections: ws→EOF/guard→parse_stmt2→progress guard→trace→semicolons→emit
   - Unconditional parse_stmt2 execution (no nested if-else)
   - Explicit `break` for loop exits

2. string_helpers.hako: StringHelpers.skip_ws simplified
   - Removed `cont` flag and guard counter
   - Direct `loop(j < n)` with `continue/break`

3. vm.rs, vm_fallback.rs: RUST_MIR_DUMP_PATH support
   - Enables offline MIR analysis for debugging

**Progress**:
-  parse_program2: infinite loop fixed
-  StringHelpers.skip_ws: infinite loop fixed
-  ParserIdentScanBox.scan_ident: next target (bb985 loop)

**Testing**:
- MIR dumps generated successfully (116K+ lines)
- ws_init loop completes
- parse_program2 progresses further
- Still hits infinite loop in scan_ident (Part 2 needed)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-24 18:19:31 +09:00
466e636af6 Span trace utilities and runner source hint 2025-11-24 14:17:02 +09:00
476c72bab8 refactor(phase27.13): Replace @ notation with local variables in UsingResolverBox
- Replace 3 instances of @ notation in _read_file method:
  - @fb → local fb
  - @ok → local ok
  - @content → local content

Result:
-  Build success: cargo build --release (warnings only)
-  Tests: 2/2 existing tests pass (type_sanity, empty_module_returns_none)
- ⚠️ auto_lowering test still blocked by 'using' keyword parser error (separate issue)

Phase 27.13 JoinIR lowering implementation is complete.
Parser fixes needed for full test enablement.
2025-11-24 03:33:11 +09:00
2692eafbbf feat(mir): Phase 26-H JoinIR型定義実装完了 - ChatGPT設計
## 実装内容(Step 1-3 完全達成)

### Step 1: src/mir/join_ir.rs 型定義追加
- **JoinFuncId / JoinContId**: 関数・継続ID型
- **JoinFunction**: 関数(引数 = φノード)
- **JoinInst**: Call/Jump/Ret/Compute 最小命令セット
- **MirLikeInst**: 算術・比較命令ラッパー
- **JoinModule**: 複数関数保持コンテナ
- **単体テスト**: 型サニティチェック追加

### Step 2: テストケース追加
- **apps/tests/joinir_min_loop.hako**: 最小ループ+breakカナリア
- **src/tests/mir_joinir_min.rs**: 手書きJoinIR構築テスト
  - MIR → JoinIR手動構築で型妥当性確認
  - #[ignore] で手動実行専用化
  - NYASH_JOINIR_EXPERIMENT=1 トグル制御

### Step 3: 環境変数トグル実装
- **NYASH_JOINIR_EXPERIMENT=1**: 実験モード有効化
- **デフォルト挙動**: 既存MIR/LoopForm経路のみ(破壊的変更なし)
- **トグルON時**: JoinIR手書き構築テスト実行

## Phase 26-H スコープ遵守
 型定義のみ(変換ロジックは未実装)
 最小限の命令セット
 Debug 出力で妥当性確認
 既存パイプライン無影響

## テスト結果
```
$ NYASH_JOINIR_EXPERIMENT=1 cargo test --release mir_joinir_min_manual_construction -- --ignored --nocapture
[joinir/min] MIR module compiled, 3 functions
[joinir/min] JoinIR module constructed:
[joinir/min]  JoinIR型定義は妥当(Phase 26-H)
test result: ok. 1 passed; 0 failed
```

## JoinIR理論の実証
- **φノード = 関数引数**: `fn loop_step(i, k_exit)`
- **merge = join関数**: 分岐後の合流点
- **ループ = 再帰関数**: `loop_step` 自己呼び出し
- **break = 継続呼び出し**: `k_exit(i)`

## 次フェーズ (Phase 27.x)
- LoopForm v2 → JoinIR 自動変換実装
- break/continue ハンドリング
- Exit PHI の JoinIR 引数化

🌟 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: ChatGPT <noreply@openai.com>
2025-11-23 04:10:12 +09:00
0bba67a72c fix(parser): ParserBox.parse_program2 無限ループ回避 - PHI依存排除版
## 問題
- Stage-1 CLI emit_program_json で無限ループ発生
- 初期ホワイトスペーススキップループで ws_cont_init PHIバグ
- ループ条件変数への代入が Header PHI に反映されず

## 根本原因
- Header PHI generation failure
- ws_cont_init = 0 実行後もループ条件で ws_cont_init == 1 が true

## 解決策
- PHI依存を完全排除:loop(ws_cont_init == 1) → loop(i < n)
- 条件付き break だけで制御(continue/break のみ)
- Header PHI に依存しない構造に書き換え

## 変更内容
- lang/src/compiler/parser/parser_box.hako:294-312
  - loop(ws_cont_init == 1) → loop(i < n) に変更
  - if whitespace { i++; continue } else { break }
  - ws_cont_init 変数を完全削除

## Phase 26-H 準備
- この修正により Stage-1 CLI が動作可能に
- JoinIR 実装の前提条件クリア
- PHI問題の暫定回避(根治は JoinIR で行う)

🌟 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-23 04:01:23 +09:00
948f22a03a feat(phi): Phase 26-F-2 - 箱理論による責務分離(IfBodyLocalMergeBox新設)
**箱理論による問題解決**:
-  問題: LoopVarClassBox(ループスコープ分析)とif-merge処理が混在
-  解決: if-merge専用箱を新設して責務分離

**新箱: IfBodyLocalMergeBox**:
- 責務: if-merge専用のbody-local φ候補決定
- ロジック:
  - 両腕に存在する変数を検出
  - pre_ifと比較して値が変わった変数のみ
  - empty elseは空リスト返す
- 特徴: LocalScopeInspector不要、LoopVarClassBox不使用

**変更ファイル**:
- src/mir/phi_core/if_body_local_merge.rs: 新規作成(IfBodyLocalMergeBox)
- src/mir/phi_core/phi_builder_box.rs: IfBodyLocalMergeBox使用に切り替え
- src/mir/phi_core/body_local_phi_builder.rs: filter_if_merge_candidates()削除
- src/mir/loop_builder.rs: BodyLocalPhiBuilder setup削除
- src/mir/phi_core/mod.rs: if_body_local_merge追加

**テスト結果**:
- Passed: 353→354 (+1) 
- Failed: 14→14 (退行なし)

**既知の問題**:
- domination error依然残存(%48 in bb48 from bb52)
- 次フェーズで調査・修正予定

技術詳細:
- ChatGPT箱理論分析による設計
- A案ベースのシンプル実装
- 責務明確化: ループスコープ分析 vs if-merge専用処理
2025-11-22 11:03:21 +09:00
51d53c2932 wip(stage1): StringHelpers.skip_ws receiver捏造問題の応急処置
- 問題: StaticCompiler method呼び出し時にreceiver ValueIdが捏造され未定義エラー
- 応急処置: string_helpers.hako で src を明示的に文字列化 (""+src)
- 再現ケース: apps/tests/stage1_skip_ws_repro.hako 追加
- エラー: use of undefined value ValueId(28) in ParserBox.length(receiver=ValueId(28))

根本修正は次のcommitで実施:
- src/mir/builder/ssa/local.rs - receiver origin/type伝播強化
- Phase 25.1: Stage-1 bridge receiver bug (workaround)
2025-11-21 13:19:18 +09:00
227ce61de8 fix(stageb): ParserStmtBox skip_ws静的呼び出し化 - Phase 25.1
**変更内容**:
- ctx.skip_ws(src, j) → ParserStringUtilsBox.skip_ws(src, j) (20箇所)
  - ParserStmtBox.parse: 13箇所
  - ParserStmtBox.parse_using: 7箇所

**理由**:
- MIRレベルでctx(ParserBox instance)がString化する問題を根本回避
- 箱理論的に正しい設計: scan utility = static box統一
- Region+next_iパターンと一貫性維持(LoopForm v2設計準拠)

**影響範囲**:
- lang/src/compiler/parser/stmt/parser_stmt_box.hako のみ
- using追加: ParserStringUtilsBox

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-21 12:27:24 +09:00
f9d100ce01 chore: Phase 25.1 完了 - LoopForm v2/Stage1 CLI/環境変数削減 + Phase 26-D からの変更
Phase 25.1 完了成果:
-  LoopForm v2 テスト・ドキュメント・コメント完備
  - 4ケース(A/B/C/D)完全テストカバレッジ
  - 最小再現ケース作成(SSAバグ調査用)
  - SSOT文書作成(loopform_ssot.md)
  - 全ソースに [LoopForm] コメントタグ追加

-  Stage-1 CLI デバッグ環境構築
  - stage1_cli.hako 実装
  - stage1_bridge.rs ブリッジ実装
  - デバッグツール作成(stage1_debug.sh/stage1_minimal.sh)
  - アーキテクチャ改善提案文書

-  環境変数削減計画策定
  - 25変数の完全調査・分類
  - 6段階削減ロードマップ(25→5、80%削減)
  - 即時削除可能変数特定(NYASH_CONFIG/NYASH_DEBUG)

Phase 26-D からの累積変更:
- PHI実装改善(ExitPhiBuilder/HeaderPhiBuilder等)
- MIRビルダーリファクタリング
- 型伝播・最適化パス改善
- その他約300ファイルの累積変更

🎯 技術的成果:
- SSAバグ根本原因特定(条件分岐内loop変数変更)
- Region+next_iパターン適用完了(UsingCollectorBox等)
- LoopFormパターン文書化・テスト化完了
- セルフホスティング基盤強化

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: ChatGPT <noreply@openai.com>
Co-Authored-By: Task Assistant <task@anthropic.com>
2025-11-21 06:25:17 +09:00
baf028a94f docs(phi): Phase 25.1 - LoopForm v2 コメント整備 + ケース表完成
-  [LoopForm] タグで統一コメント追加
  - src/mir/loop_builder.rs
    - header-cond: Case A/B分岐説明
    - exit-break path / continue-backedge path
    - exit PHI for Case A/B
  - src/mir/phi_core/loop_snapshot_merge.rs
    - Case A/B分岐: header ∈ exit_preds判定ロジック
  - src/mir/phi_core/exit_phi_builder.rs
    - LoopForm Process ステップバイステップ説明

-  UsingCollectorBox Region+next_i化
  - lang/src/compiler/parser/using/using_collector_box.hako
    - 全ループをLoopForm v2形式に統一
    - next_i, next_j, next_k, next_t パターン導入
    - SSA安全化(未定義変数撲滅)

-  LoopForm v2 ケース表完成
  - docs/development/architecture/loops/loopform_ssot.md
    - Case A/B/C/D の完全な表
    - テスト対応マッピング
    - 実装ファイル対応表

🎯 成果: LoopForm v2の「形」をソース・テスト・ドキュメントで完全固定
2025-11-21 06:22:21 +09:00
471052ad8d feat(debug): __mir__.log追加+VM実行テスト - loopバグ確定
## 🔍 func_scanner.hakoに__mir__.log追加
```hako
method skip_whitespace(s, idx) {
  __mir__.log("skip_ws/head", i, n)
  loop(1 == 1) {
    __mir__.log("skip_ws/loop", i, n)  ← 実行されない
    ...
  }
  __mir__.log("skip_ws/exit", i, n)
}
```

## 📊 CLI実行結果(MIRログ)
```
[MIR-LOG] skip_ws/head: %26=Integer(0) %28=Integer(6)
[MIR-LOG] skip_ws/exit: %26=Integer(0) %28=Integer(6)
```
-  i=0, n=6(両方Integer, 値は正しい)
-  `skip_ws/loop`が**一度も出ない**
- → **loop本体が実行されていないことがMIRレベルで確定**

## 🧪 Rustテスト更新
1. **ソースを束ねる**: func_scanner.hako + test file
   - FuncScannerBox関数がmoduleに含まれるように修正
2. **VM実行追加**: execute_module()でバグ再現確認
   - 期待: rc=0 (PASS), 実際: rc=1 (FAIL)

## 🎯 次のステップ
- MIRダンプでLoopForm展開を確認
- VM interpreter/LoopForm実行を調査

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 08:22:43 +09:00
7ed13f98d5 test(stageb): 最小再現ケース+Rustテスト追加 - using読み込み問題発見
## 🔍 新規ファイル
1. **funcscanner_skip_ws_min.hako**: 最小再現ケース
   - FuncScannerBox.skip_whitespace直接呼び出しテスト
   - 期待: idx=3(3空白スキップ)
   - 実際: idx=0(loop不実行でFAIL)

2. **mir_funcscanner_skip_ws.rs**: Rustレベルテスト
   - MIRコンパイル + 検証
   - 関数存在確認

## 🐛 重大発見
### 問題: using経由モジュールが読み込まれない
```
[test] Module has 2 functions
[test] ALL available functions:
[test]   - main
[test]   - condition_fn
```
- `using lang.compiler.entry.func_scanner as FuncScannerBox`宣言済み
- でもFuncScannerBox.skip_whitespace/2が**モジュールに存在しない**
- CLI実行時は動作 → Rustテスト環境特有の問題?

### 2層の問題構造
1. **本命バグ**: loop(1==1)が実行されない(CLI実行で再現済み)
2. **新発見**: usingモジュール読み込み未実装(Rustテスト環境)

## 📊 次のステップ
- using systemのコンパイル時モジュール解決を調査
- または別アプローチでloop バグに直接アプローチ

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 08:16:35 +09:00
0dc8510daf debug(stageb): センチネル追加でVMバグ特定 - using経由static box内loop不実行
## 🔍 調査結果
###  確認事項
- **本物の実装が呼ばれている**: SENTINEL出力で確認済み
  - 🔥 SENTINEL_SKIP_WS_CALLED!!!
  - 🎯 SENTINEL_KW_BOUNDARY_BEFORE_CALLED!!!
  - 🎯 SENTINEL_KW_BOUNDARY_AFTER_CALLED!!!
  - 🔤 SENTINEL_IS_IDENT_CHAR_CALLED!!!

### 🐛 重大バグ発見
**症状**: `FuncScannerBox.skip_whitespace` 内の `loop(1 == 1)` が実行されない

**証拠**:
```
[skip_ws] START idx=10 s.length()=173
[skip_ws] i=10 n=173
[skip_ws] RETURN i=10  ← ループボディが実行されず即座にreturn
```
- `[skip_ws] LOOP-TOP i=10` が**一度も出力されない**
- loop(1 == 1) の無限ループすら実行されない

**影響範囲**:
- box_name抽出失敗(空文字列)
- defs生成失敗(defs_len=0)
- canary テスト失敗

**問題の本質**:
- using 経由で読み込まれたモジュールの static box 内
- 静的メソッド呼び出し (`FuncScannerBox.skip_whitespace(...)`)
- loop 構文が VM/MIR レベルで実行されない

## 🔧 修正内容
1. **センチネル追加**: 4箇所に明確な出力追加
   - skip_whitespace, kw_boundary_before, kw_boundary_after, is_ident_char
2. **呼び出し修正**: `me.scan_all_boxes` → `StageBFuncScannerBox.scan_all_boxes`

## 📊 次のステップ
VM/MIR レイヤーでの loop 構文実装確認が必要

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 08:03:05 +09:00
54b2735f13 refactor(stageb): FuncScannerBox完全静的化 - new()撤廃でSSOT確立
## 構造改善
-  `new FuncScannerBox()` 完全撤廃(8箇所削除)
-  FuncScannerBox を純粋静的ヘルパー箱化
-  StageBFuncScannerBox を薄いデリゲートファサードに
-  全 `me.*` 呼び出しを `FuncScannerBox.*` 静的呼び出しに変換

## エラー解決
-  "Unknown method on InstanceBox" エラー根絶
-  "Type error: unsupported compare Lt on String" エラー解決
-  VM実行時の全エラー解消

## SSOT構造
FuncScannerBox (SSOT)
  ├─ 公開メソッド: skip_whitespace, find_matching_brace, 等
  ├─ 静的ヘルパーエイリアス: _parse_params, _strip_comments, 等
  └─ 内部実装: すべて FuncScannerBox.* 静的呼び出し

StageBFuncScannerBox (薄いファサード)
  └─ 全メソッドが FuncScannerBox への静的委譲のみ

## 未解決問題
- ⚠️ box_name 抽出が空文字列を返す(box検出は成功、名前抽出が失敗)
- ⚠️ defs_len=0 のまま(box_name='' のため _scan_methods が呼ばれない)

次のステップ: box_name抽出ロジックのデバッグ

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 07:45:28 +09:00
e809d3a79b refactor(stageb): Phase 25.3 FuncScanner boxification完了
- FuncScannerBox helper SSOT確立(8個のhelperに詳細コメント追加)
- StageBFuncScannerBox → FuncScannerBox完全委譲(約380行削減)
- scan_all_boxes状態フラグ整理(4つの状態遷移を明確化)
- 常時出力print削除(dev専用ログのみ保持)
- SSAテスト全pass(mir_funcscanner_scan_methods/fib_min)

Phase 25.3-B完了、次はfib defs canary緑化へ

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 07:01:21 +09:00
3a82633924 refactor(funcscanner): Region+next_i パターン統一 & SSA テスト追加
**FuncScanner .hako 側改善**:
- scan_all_boxes を Region + next_i 形式に統一(continue 多発による SSA/PHI 複雑さ削減)
- インデント修正(タブ→スペース統一)
- デバッグ print 削除

**SSA テスト追加**:
- lang/src/compiler/tests/funcscanner_scan_methods_min.hako
- src/tests/mir_funcscanner_ssa.rs (scan_methods & fib_min SSA デバッグテスト)

**Phase 25.3 ドキュメント**:
- docs/development/roadmap/phases/phase-25.3-funcscanner/ 追加

**関連**: Phase 25.3 FuncScanner 箱化準備作業

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 06:38:43 +09:00
7373fa265b feat(loop-phi): Phase 25.1c/k - continue_merge PHI生成完了
## 実装内容

### 1. continue_merge ブロックで PHI ノード生成
- `src/mir/loop_builder.rs` (422-557行)
- 複数の continue パスからの変数値を PHI でマージ
- 全て同じ値なら PHI 省略(最適化)
- merged_snapshot を seal_phis に渡す構造

### 2. ValueId::INVALID GUARD 修正
- `src/mir/phi_core/loopform_builder.rs` (111行)
- 誤った `value.0 == 0` チェックを `value == ValueId::INVALID` に修正
- ValueId::INVALID は u32::MAX なので、ValueId(0) は有効な値

### 3. test_loopform_builder_separation を構造ベースに改善
- 具体的な ValueId(100..105) を期待するアサーションを削除
- pinned/carrier の分離、ValueId の有効性、衝突チェックに変更
- HashMap の反復順序や内部の割り当て順に依存しないテストに改善

## テスト結果

 **既存テスト全て PASS**:
- `test_loopform_builder_separation` - 構造ベース修正で PASS
- 既存ループ関連テスト15個 - 全て PASS
- `mir_stageb_loop_break_continue::*` - PASS
- `mir_loopform_exit_phi::*` - PASS

 **実行確認**:
- 基本的なループ実行 - 正常動作(sum=10)
- continue を含むループ実行 - 正常動作(sum=8)
- continue_merge ブロック生成確認(BasicBlockId表示)

⚠️ **残存バグ**:
- FuncScannerBox.scan_all_boxes/1: ValueId(1283) undefined
- 13個の continue を持つ複雑なループで発生
- Phase 25.2 リファクタリングで解決予定

## 今後の予定

Phase 25.2 として以下のリファクタリングを実施予定:
1. LoopSnapshotMergeBox 実装(優先度1)
2. LoopVarClassifyBox 実装(優先度2)
3. LoopDebugLogBox 実装(優先度3)
4. TextScanRegionBox 実装(優先度4)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-20 01:41:17 +09:00
525e59bc8d feat(loop-phi): Add body-local variable PHI generation for Rust AST loops
Phase 25.1c/k: Fix ValueId undefined errors in loops with body-local variables

**Problem:**
- FuncScannerBox.scan_all_boxes/1 and BreakFinderBox._find_loops/2 had ValueId
  undefined errors for variables declared inside loop bodies
- LoopFormBuilder only generated PHIs for preheader variables, missing body-locals
- Example: `local ch = s.substring(i, i+1)` inside loop → undefined on next iteration

**Solution:**
1. **Rust AST path** (src/mir/loop_builder.rs):
   - Detect body-local variables by comparing body_end_vars vs current_vars
   - Generate empty PHI nodes at loop header for body-local variables
   - Seal PHIs with latch + continue snapshot inputs after seal_phis()
   - Added HAKO_LOOP_PHI_TRACE=1 logging for debugging

2. **JSON v0 path** (already fixed in previous session):
   - src/runner/json_v0_bridge/lowering/loop_.rs handles body-locals
   - Uses same strategy but for JSON v0 bridge lowering

**Results:**
-  FuncScannerBox.scan_all_boxes: 41 body-local PHIs generated
-  Main.main (demo harness): 23 body-local PHIs generated
- ⚠️ Still some ValueId undefined errors remaining (exit PHI issue)

**Files changed:**
- src/mir/loop_builder.rs: body-local PHI generation logic
- lang/src/compiler/entry/func_scanner.hako: debug logging
- /tmp/stageb_funcscan_demo.hako: test harness

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 23:12:01 +09:00
75f3df2505 refactor(mir): Phase 25.1o - do_break/continue 共通化(LoopExitKind型統一)
【変更内容】
1. LoopExitKind enum定義
   - Break / Continue の型安全な区別

2. do_loop_exit() 共通メソッド作成(47行)
   - スナップショット取得(共通処理)
   - kind別のスナップショット保存
   - kind別のジャンプターゲット
   - unreachable ブロック切り替え(共通処理)

3. do_break/continue をthin wrapperに変換
   - do_break: 13行 → 4行
   - do_continue: 12行 → 4行
   - 合計21行削減

【効果】
- 構造改善: break/continue の共通ロジック一箇所に集約
- 保守性向上: デバッグログなどの共通処理が統一管理
- 拡張性向上: labeled break/continue等の将来拡張が容易

【検証結果】
- ビルド成功(警告なし)
- mir_stageb_loop_break_continue_verifies: PASS
- /tmp/loop_continue_fixed.hako: RC=3(期待通り)

関連: Phase 25.1m (continue PHI修正), Phase 25.1n (レガシー削除)
2025-11-19 08:56:44 +09:00
a95fedf26a fix(mir): Phase 25.1m - Continue PHI修正 & Bug A main(args)ループ修正
**Phase 25.1m: Continue PHI修正**
- seal_phis に continue_snapshots 入力を追加 (loopform_builder.rs)
- LoopShape::debug_validate に continue/break エッジ検証追加 (control_form.rs)
- test_seal_phis_includes_continue_snapshots テスト追加
- 実証テスト成功: balanced scan loop で 228回イテレーション確認

**Bug A修正: main(args) でループ未実行問題**
- LoopBuilder::build_loop で entry → preheader への jump 追加
- decls.rs でデュアル関数作成時のブロック接続修正
- mir_static_main_args_loop.rs テスト追加

**パーサー改善**:
- parser_box.hako に HAKO_PARSER_PROG_MAX ガード追加(無限ループ対策)

🎉 成果:
- Continue 文の PHI predecessor mismatch エラー完全解消
- main(args) パラメータ有りループが正常動作
- Stage-B balanced scan で continue 正常動作確認 (228回イテレーション)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 08:04:43 +09:00
b086933acb debug(stageb): Phase 25.1c balanced scan診断トレース追加→VM continue バグ特定
Task 8-4: balanced scan loopハング根本原因特定完了

**診断トレース追加内容**:
- balanced scan loop開始前トレース (k3, len)
- 全イテレーション進捗トレース (#N, i, depth)
- substring呼び出し前後トレース
- 各分岐処理トレース (open-brace, close-brace, quote, other)

**根本原因特定**:
```
[stageb/body/iter] #1 i=231 depth=0
[stageb/body/substr-pre] #1 calling s.substring(231, 232)
[stageb/body/substr-post] #1 got ch
[stageb/body/branch] open-brace depth=0->+1 i=231->+1
# ここでハング - #2イテレーショントレースが出ない
```

**確定事項**:
1.  `s.substring(231, 232)` 成功
2.  `ch == "{"` 分岐に入った
3.  `depth=0->1`, `i=231->232` 実行
4.  `continue` 実行したはず
5.  **ループ先頭に戻らず、2回目のトレースが出ない**

**結論**:
- Stage-B/.hakoコードの問題ではない
- substringパフォーマンスの問題でもない
- **Rust VM の loop/continue 制御フローにバグ**

**次のステップ**: Phase 25.1m/25.1d拡張タスクとして、
LoopForm v2 + VM continue バグ修正をRustテストで再現・修正

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 06:17:24 +09:00
8054875261 feat(parser): Phase 25.1c dev-only progress guard実装
Task 8-4: ParserBox.parse_program2ハング調査のため、開発専用の進捗ガード実装

**実装内容**:
- HAKO_PARSER_PROG_MAX環境変数で最大反復回数を設定可能
- デフォルト挙動は完全不変(max_prog=0=無制限)
- 数値パースは安全実装(不正値→0扱い)
- トレースモード時のみガード到達をログ出力

**Phase 25ポリシー準拠**:
- 仕様変更なし(dev-onlyオプトイン)
- 既存コード完全互換
- 無効値は静かに無視(デフォルト挙動維持)

**調査状況**:
- Hotfix 8適用後、Stage-Bトレースは after_build_body_src まで出力
- parse_program2に入っておらず、パーサートレース未出現
- trace_enabled()呼び出し前後のハング疑惑を調査中

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 05:48:51 +09:00
dad278caf2 feat(hotfix-8): Fix static method receiver detection logic (Hotfix 4 inversion bug)
## Issue
- StageBTraceBox.log("label") passed null for the label parameter
- Static methods incorrectly detected as having implicit receiver
- Hotfix 4 logic was inverted: `!matches!(params[0], MirType::Box(_))`

## Root Cause
src/mir/function.rs:90-101 had inverted logic:
- Instance methods (params[0]: Box type) → should have receiver
- Static methods (params[0]: non-Box type) → should NOT have receiver
- Previous code: `!matches!()` = true for non-Box → receiver=true (WRONG)

## Fix
- Changed `!matches!(signature.params[0], MirType::Box(_))` to
  `matches!(signature.params[0], MirType::Box(_))`
- Updated comments to clarify instance vs static method detection
- Result: static methods now correctly have receiver=0

## Verification
Before: fn='StageBTraceBox.log/1' params=1, receiver=1, total=2 
After:  fn='StageBTraceBox.log/1' params=1, receiver=0, total=1 

Test output:
Before: [stageb/trace]           # label=null
After:  [stageb/trace] test_label # label passed correctly 

## Files Changed
- src/mir/function.rs: Fixed has_implicit_receiver logic
- lang/src/compiler/entry/compiler_stageb.hako: Added guaranteed entry marker
  and direct print traces for Phase 25.1c debugging
- CURRENT_TASK.md: Updated task progress

## Phase 25.1c Progress
- Hotfix 8 完了:static method parameter passing 修正
- Stage-B トレース正常動作確認
- 次のタスク:ParserBox.parse_program2 ハング問題調査

🐾 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 05:30:31 +09:00
fa571a656e feat(stageb): Phase 25.1c - Stage-B トレース追加(dev-only)
追加内容:
- StageBTraceBox: dev トレース用 Box 追加(HAKO_STAGEB_TRACE=1 で有効)
- トレースポイント:
  - StageBArgsBox.resolve_src: enter/return_len
  - StageBBodyExtractorBox.build_body_src: enter_len/return_len
  - StageBDriverBox.main: enter/after_resolve_src/after_build_body_src/
    after_parse_program2/func_scan methods/exit rc=0

Phase 25.1c 目標:
- Stage-B / Stage-1 CLI 構造デバッグ
- fib canary / selfhost CLI canary の rc=1 原因特定

ポリシー:
- dev env でガード(挙動不変)
- 既定挙動は変更せず、観測のみ追加

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-19 04:49:25 +09:00
39f5256c18 📊 Phase 25.1l: Region観測レイヤー骨格 + スコープ契約設計理解
**Region Box統一理論の実装開始**

新規追加:
- src/mir/region/mod.rs: Region/RefSlotKind型定義
- src/mir/region/observer.rs: Region観測レイヤー
- docs/development/roadmap/phases/phase-25.1l/: 設計ドキュメント

主要概念:
- Region Box = Function/Loop/If の統一箱
- RefSlotKind = GC管理用スロット種別(Strong/Weak/Borrowed/NonRef)
- 観測専用(NYASH_REGION_TRACE=1で動作、挙動変更なし)

設計理解の深化:
- ValueId(40)問題 = LoopForm v2スコープ契約違反の症状
- 根本解決 = Region観測で無名一時値のスコープまたぎを検出
- 箱理論3原則: 境界明確化/差し替え可能/段階的移行

関連議論:
- ChatGPT提案: Region統一理論でGC/寿命管理の基盤構築
- SlotRegistry: 変数の単一真実源(SSOT)
- 階層構造: FunctionRegion → LoopRegion → IfRegion

次のステップ:
- Phase 1: Region観測(現在)- 非破壊的追加
- Phase 2: メタデータ出力(MIR JSON拡張)
- Phase 3: GC統合(retain/release挿入)

テスト追加:
- lang/src/compiler/tests/stageb_mini_driver.hako
- tools/test_loopssa_breakfinder_slot.sh

Build:  全警告は既存のもの
Tests: 既存テスト全て緑維持
2025-11-19 02:44:40 +09:00
80f8a7bc8c 🔧 Hotfix 7 (Enhanced): ValueId receiver alias tracking for nested loops
- Problem: Pinned receiver variables in loops cause undefined ValueId errors
- Enhanced fix: Update all receiver aliases (me + all __pin$N$@recv levels)
- Handles nested loops by updating previous pin levels
- Test status: Partial improvement, ValueId(50) → ValueId(40)
- Further investigation needed for complete fix

Files modified:
- src/mir/phi_core/loopform_builder.rs (emit_header_phis)
2025-11-19 00:02:41 +09:00
5bb094d58f feat(.hako): Exit PHI実装(Phase 2-5完了)- リファレンス実装
.hakoコンパイラにExit PHI生成機能を実装(将来の本命実装)

実装ファイル(585行):
- break_finder.hako (~250行): break文検出
- phi_injector.hako (~280行): PHI命令生成・挿入
- loopssa.hako (更新): BreakFinder/PhiInjector統合
- README.md: アーキテクチャ説明・使用方法

設計:
- 箱化・モジュール化(3Box分離)
- JSON文字列→文字列処理
- HAKO_LOOPSSA_EXIT_PHI=1 で有効化

重要な発見:
- Exit PHI生成はMIRレベルで行うべき(JSON v0では情報不足)
- 現在のTest 2エラーはRust MIRビルダーのバグ
- .hako実装は将来のリファレンス・Phase 25.1f用に温存

次のステップ:
- Rust側 loopform_builder.rs のphi pred mismatchバグ修正
- .hakoへの完全移行はPhase 25.1e後半〜25.1f

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-18 04:05:45 +09:00
9f45ebaced feat(.hako): CompilerBuilder.apply_all()配線追加 (Phase 1)
Exit PHI実装の準備として、.hakoコンパイラに
CompilerBuilder.apply_all()呼び出しを追加

変更内容:
- compiler_stageb.hako: parse_program2直後にapply_all()配線
- hako_module.toml: builder.mod export追加
- nyash.toml: モジュールマッピング追加

デバッグ:
- HAKO_COMPILER_BUILDER_TRACE=1 で詳細ログ出力
- [compiler-builder] before/after で変換前後を確認可能

次のステップ:
- Phase 2: BreakFinderBox実装
- Phase 3: PhiInjectorBox実装
- Phase 4: LoopSSA.stabilize_merges実装

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-18 03:37:47 +09:00
f3cd815c77 feat(parsercontrol): add shallow recursion guards to ParserControlBox (if/loop/break/continue/block) 2025-11-17 18:23:00 +09:00
978890e7f6 feat(parserstmt): add shallow recursion guard to ParserStmtBox.parse 2025-11-17 18:20:29 +09:00
04524f5894 feat(parserbox): add shallow recursion guard to parse_program2 for Stage-B 2025-11-17 18:11:15 +09:00
3c3e734f49 feat(stageb): add shallow recursion guards to bundle and using resolvers 2025-11-17 18:00:44 +09:00
bcefdad9eb feat(stageb): add shallow recursion guards to StageB driver/body extractor 2025-11-17 17:57:54 +09:00
c8bbe389da test(compiler): add Stage-B minimal SSA test harness
**Goal**: Create 100-line minimal test case to reproduce SSA/ValueId
bugs in Stage-B compilation without the complexity of full compiler_stageb.hako.

**Files added**:

1. **lang/src/compiler/tests/stageb_min_sample.hako** (65 lines)
   - Pattern 1: Method call in if-block before loop (TestArgs.process)
   - Pattern 2: Simple method calls without loops (TestSimple.run)
   - Pattern 3: Nested if/loop with method calls (TestNested.complex)
   - All patterns reproduce ValueId SSA bugs

2. **tools/test_stageb_min.sh** (executable test script)
   - Test 1: Direct VM execution
   - Test 2: Stage-B compilation pipeline
   - Test 3: MIR verification

**Test results** (as of commit):

Test 1 (Direct VM):
```
 ValueId(14) error in TestArgs.process/1
   (different from ValueId(17) in Stage-B!)
```

Test 2 (Stage-B):
```
 ValueId(17) error in StageBArgsBox.resolve_src/1
   (expected, same as full compiler_stageb.hako)
```

Test 3 (MIR verification):
```
 No verification errors
   (verifier doesn't catch these specific SSA bugs)
```

**Findings**:
- Multiple ValueId SSA bugs exist (14, 17, etc.)
- MIR verifier needs enhancement to catch receiver use-before-def
- Minimal harness successfully reproduces issues for easier debugging

**Next steps** (not in this commit):
- Fix ValueId(14) in TestArgs.process
- Fix ValueId(17) in StageBArgsBox.resolve_src
- Enhance MIR verifier to catch Method receiver SSA bugs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 04:29:10 +09:00
b4cb516f6a refactor(compiler): reorganize StageBBodyExtractorBox structure
**Goal**: Improve readability of 480-line build_body_src method with
clear phase separators, consistent spacing, and unified formatting.
**Zero logic changes** - behavior 100% identical.

**Structure improvements**:

1. **Added clear phase separators** with ==== comment lines:
   - Phase 4: Body extraction (k0/k1/k2/k3 logic)
   - Phase 4.7: Comment removal
   - Phase 4.5: Bundle resolution
   - Phase 4.6: Duplicate bundle check
   - Bundle merge + line-map debug output
   - Using resolver
   - Phase 5: Trim (left/right)

2. **Improved readability**:
   - Added consistent spacing between phases (2 blank lines)
   - Unified indentation (2 spaces throughout)
   - Grouped related debug blocks together
   - Made block structure more visible

3. **Zero logic changes**:
   - All variable names unchanged
   - All conditions unchanged
   - All calculations unchanged
   - All DEBUG messages unchanged
   - All bundle/using resolver calls unchanged

**Verification**:
- Same ValueId(17) error as before (expected, will fix in Task B)
- Debug logs identical ([plugin/missing], [DEBUG])
- Behavior 100% identical to original

**Impact**: Code now much more maintainable with clear phase boundaries,
making future modifications safer and simpler.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 04:19:17 +09:00
e2c37f06ba refactor(compiler): split Main into 4 boxes (Phase 25.1c)
**Goal**: Reorganize compiler_stageb.hako from monolithic Main.main
(605 lines) into 4 cleanly separated boxes following "Box Theory".

**Structure** (605→628 lines, +23 for box boundaries):

1. **StageBArgsBox** (lines 18-46)
   - Purpose: CLI argument → source resolution
   - Method: resolve_src(args)
   - Handles: --source, --source-file, env variables, defaults

2. **StageBBodyExtractorBox** (lines 48-528)
   - Purpose: Body extraction + bundle + using + trim
   - Method: build_body_src(src, args)
   - Handles: Method body extraction, comment stripping, bundling,
     using resolution, whitespace trimming

3. **StageBDriverBox** (lines 530-619)
   - Purpose: Main driver logic
   - Method: main(args)
   - Orchestrates: ParserBox setup, parse_program2, defs scanning,
     JSON output

4. **Main** (lines 623-628)
   - Purpose: Entry point (thin wrapper)
   - Method: main(args)
   - Action: Simple delegation to StageBDriverBox.main(args)

**Constraints respected**:
-  Behavior unchanged (same output JSON, same logs)
-  Code moved as-is (no logic changes)
-  All using statements preserved
-  All comments preserved + Phase 25.1c markers added
-  Proper 2-space indentation maintained
-  Call chain: Main → StageBDriverBox → StageBArgsBox/StageBBodyExtractorBox

**Verification**:
- Same ValueId(17) error occurs (expected, not fixed in this task)
- Error location changed: fn=Main.main → fn=StageBArgsBox.resolve_src/1
  (proves code was successfully moved)
- No new errors introduced
- Structural separation enables future SSA/ValueId fixes

**Impact**: Establishes clean box boundaries for future maintenance,
making it easier to debug and fix SSA issues independently per box.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 04:03:29 +09:00
eadde8d1dd fix(mir/builder): use function-local ValueId throughout MIR builder
Phase 25.1b: Complete SSA fix - eliminate all global ValueId usage in function contexts.

Root cause: ~75 locations throughout MIR builder were using global value
generator (self.value_gen.next()) instead of function-local allocator
(f.next_value_id()), causing SSA verification failures and runtime
"use of undefined value" errors.

Solution:
- Added next_value_id() helper that automatically chooses correct allocator
- Fixed 19 files with ~75 occurrences of ValueId allocation
- All function-context allocations now use function-local IDs

Files modified:
- src/mir/builder/utils.rs: Added next_value_id() helper, fixed 8 locations
- src/mir/builder/builder_calls.rs: 17 fixes
- src/mir/builder/ops.rs: 8 fixes
- src/mir/builder/stmts.rs: 7 fixes
- src/mir/builder/emission/constant.rs: 6 fixes
- src/mir/builder/rewrite/*.rs: 10 fixes
- + 13 other files

Verification:
- cargo build --release: SUCCESS
- Simple tests with NYASH_VM_VERIFY_MIR=1: Zero undefined errors
- Multi-parameter static methods: All working

Known remaining: ValueId(22) in Stage-B (separate issue to investigate)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 00:48:18 +09:00
7ca7f646de Phase 25.1b: Step2完了(FuncBodyBasicLowerBox導入)
Step2実装内容:
- FuncBodyBasicLowerBox導入(defs専用下請けモジュール)
- _try_lower_local_if_return実装(Local+単純if)
- _inline_local_ints実装(軽い正規化)
- minimal lowers統合(Return/BinOp/IfCompare/MethodArray系)

Fail-Fast体制確立:
- MirBuilderBox: defs_onlyでも必ずタグ出力
- [builder/selfhost-first:unsupported:defs_only]
- [builder/selfhost-first:unsupported:no_match]

Phase構造整備:
- Phase 25.1b README新設(Step0-3計画)
- Phase 25.2b README新設(次期計画)
- UsingResolverBox追加(using system対応準備)

スモークテスト:
- stage1_launcher_program_to_mir_canary_vm.sh追加

Next: Step3 LoopForm対応

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-15 22:32:13 +09:00
6856922374 Phase 25.1a: selfhost builder hotfix (fn rename, docs) 2025-11-15 05:42:32 +09:00
f1fa182a4b AotPrep collections_hot matmul tuning and bench tweaks 2025-11-14 13:36:20 +09:00
647ee05d06 fix(emit): stabilize Stage-B wrapper with temp file approach
Root Cause:
- Subshell CODE expansion became path literal "/cat/tmp/matmul.hako"
- Variable lost in nested subshell with cd command
- All benchmark cases (matmul, arraymap, etc.) failed emit

Solution:
- Temp file approach with trap cleanup (CODE_TMP=$(mktemp))
- 3-tier fallback extraction (Python→awk→ruby)
- Enhanced diagnostics with HAKO_SELFHOST_TRACE=1
- Pre-check SKIP logic in microbench for unstable emit

Changes:
- tools/hakorune_emit_mir.sh
  - Temp file approach eliminates subshell variable issues
  - extract_program_json now has 3 fallback strategies
  - Detailed trace output for debugging
  - Variable scope fixes (local → script level)
- tools/perf/microbench.sh
  - matmul pre-check with SKIP + diagnostic hint
  - Prevents false benchmark results on emit failure

Test Results:
 loop:        936 bytes   rc=0
 call:        330 bytes   rc=0
 stringchain: 313 bytes   rc=0
 arraymap:    422 bytes   rc=0
 matmul:     7731 bytes   rc=0 (FIXED!)
 CI guard: emit_provider_no_jsonfrag_canary PASS

Impact:
- All benchmark cases now emit MIR successfully
- Stable execution without subshell variable bugs
- Comprehensive diagnostics for future debugging
- Foundation for provider-first optimization

Next: Apply AotPrep to optimize Array/Map hot paths

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 22:52:25 +09:00
801833df8d fix(env): improve Environment::set scope resolution (partial)
Fixed:
- Environment::set now properly searches ancestor chain before creating new binding
- Added exists_in_chain_locked() helper for explicit existence checking
- Simple {} blocks now correctly update outer scope variables

Verified Working:
- local x = 10; { x = 42 }; print(x) → prints 42 

Still Broken:
- else blocks don't update outer scope variables
- local x = 10; if flag { x = 99 } else { x = 42 }; print(x) → prints 10 

Root Cause Identified:
- Issue is in MIR Builder (compile-time), not Environment (runtime)
- src/mir/builder/if_form.rs:108 resets variable_map before else block
- PHI generation at merge doesn't use else_var_map_end correctly
- MIR shows: phi [%32, bb1], [%1, bb2] where %1 is original value, not else value

Next: Fix else block variable merging in if_form.rs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 18:55:14 +09:00
1ac0c6b880 feat(stageb): implement UsingResolverBox foundation (partial)
Implemented:
- UsingResolverBox full implementation in using_resolver_box.hako
  - state_new(): Empty state creation
  - load_modules_json(): Load modules JSON from nyash.toml
  - resolve_path_alias(): Resolve paths from aliases
  - resolve_namespace_alias(): Tail segment matching with case-insensitive support
  - to_context_json(): Generate context JSON for ParserBox
- Added sh_core entry to nyash.toml modules section
  - Maps to lang/src/shared/common/string_helpers.hako
  - Fixes "using not found: 'sh_core'" errors
- Cleaned up compiler_stageb.hako
  - Removed problematic using statements
  - Added documentation

Known Issue (to be fixed next):
- Body extraction bug in compiler_stageb.hako:51-197
  - Multiline source extraction fails for "static box Main { main() {...} }"
  - Results in empty Program JSON body
  - Causes Stage-B emit pipeline to fall back to jsonfrag (ratio=207900%)
  - This is the root cause blocking selfhost builder path

Impact:
-  sh_core resolution errors fixed
-  UsingResolverBox infrastructure complete
-  Stage-B emit pipeline not restored (body extraction bug)
-  Selfhost builder path still blocked

Next Priority: Fix body extraction bug to restore Stage-B pipeline

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 18:11:25 +09:00
9e2fa1e36e Phase 21.6 solidification: chain green (return/binop/loop/call); add Phase 21.7 normalization plan (methodize static boxes). Update CURRENT_TASK.md and docs. 2025-11-11 22:35:45 +09:00
52b62c5772 feat(phase21.5): Stage-B parser loop fix + delegate path stabilization
## 修正内容

### 1. Stage-B パーサー修正(偶然の回避)
- **ファイル**:
  - `lang/src/compiler/parser/expr/parser_expr_box.hako`
  - `lang/src/compiler/parser/stmt/parser_control_box.hako`
- **問題**: ネストループで gpos が正しく進まず、loop の cond/body が壊れる
- **回避策**: new 式のメソッドチェーン処理追加で別ループを導入
- **結果**: MIR 生成が変わって VM gpos バグを回避

### 2. delegate パス動作確認
- **テスト**: `/tmp/loop_min.hako` → rc=10 
- **MIR構造**: 正しい PHI/compare/binop を生成
- **チェーン**: hakorune parser → Rust delegate → LLVM EXE 完動

### 3. ドキュメント追加
- `docs/development/analysis/` - delegate 分析
- `docs/development/guides/` - ループテストガイド
- `docs/development/testing/` - Stage-B 検証報告

### 4. カナリーテスト追加
- `tools/smokes/v2/profiles/quick/core/phase2100/` 配下に複数追加
- emit_boxcall_length_canary_vm.sh
- stageb_parser_loop_json_canary_vm.sh
- 他

### 受け入れ基準
-  delegate パス: rc=10 返す
-  FORCE パス: rc=10 返す(既存)
-  MIR 構造: 正しい PHI incoming と compare
-  既定挙動: 不変(dev トグルのみ)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-11 21:24:51 +09:00