hakorune/MIR13_MODE.md at 981ddd890c75934df7a6502b51d936409e7fa0be

Files

Selfhosting Dev 9b9a91c859 feat: GC機能復活＆VM整理＆json_native調査完了

## 🎉 ChatGPT×Claude協働成果
- ✅ **GC機能復活**: vm-legacy削除で失われたGC機能を新実装で復活
  - GCメトリクス追跡システム実装（alloc/collect/pause計測）
  - 3種類のGCモード対応（counting/mark_sweep/generational）
  - host_handles.rsでハンドル管理復活

- ✅ **VM整理とエイリアス追加**: 混乱していた名前を整理
  - MirInterpreter = NyashVm = VM のエイリアス統一
  - vm-legacyとインタープリターの違いを明確化
  - 壊れていたvm.rsの互換性修復

- ✅ **スモークテスト整理**: v2構造でプラグイン/コア分離
  - plugins/ディレクトリにプラグインテスト移動
  - gc_metrics.sh, gc_mode_off.sh, async_await.sh追加
  - _ensure_fixture.shでプラグイン事前ビルド確認

## 📊 json_native調査結果
- **現状**: 25%完成（配列/オブジェクトパース未実装）
- **将来性**: 並行処理でyyjson超えの可能性大
  - 100KB以上のJSONで2-10倍速の可能性
  - Nyash ABI実装後はゼロコピー最適化
- **判断**: 現時点では置換不可、将来の大きな足場

## 🔍 技術的発見
- vm-legacy = 完全なVM実装（GC付き）だった
- MirInterpreter = 現在のRust VM（712行、Arc使用）
- 200行簡易JSONは既に削除済み（存在しない）

ChatGPT爆速修復×Claude詳細調査の完璧な協働！

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

Co-Authored-By: Claude <noreply@anthropic.com>

2025-09-24 23:27:59 +09:00

2.8 KiB

Raw Blame History

MIR13 Mode (legacy PHI-off fallback)

Overview

Goal: Retain the Phase‑14 edge-copy compatibility path for debugging historical MIR dumps or diagnosing SSA regressions.
Default: MIR14 (PHI-on) now ships as the standard. MIR13 must be explicitly enabled through environment flags.

Why keep MIR13 around?

Reproducibility: Some archived JSON v0 fixtures were captured before PHI-on shipped. MIR13 allows replaying them without regeneration.
Diagnostics: Edge-copy runs make it easier to isolate builder regressions by removing PHI synthesis from the equation.
Tooling parity: Certain scripts still compare MIR13 traces; they will be retired once PHI-on parity checks are complete.

Flags and Behavior

NYASH_MIR_NO_PHI (default: 0)
- 0: Builders emit PHIs at merge heads (MIR14, default).
- 1: Builders drop PHIs and insert per-predecessor edge copies (MIR13 fallback).
NYASH_VERIFY_ALLOW_NO_PHI (default: 0 unless PHI-off is requested)
- Set this to 1 together with NYASH_MIR_NO_PHI=1 when you intentionally relax SSA verification.
NYASH_LLVM_USE_HARNESS=1 (AOT via llvmlite harness)
- In MIR13 mode the harness synthesizes PHIs. In MIR14 it simply validates incoming edges.

LLVM (llvmlite) Responsibilities

setup_phi_placeholders(): still records declared PHIs; in MIR13 mode it creates placeholders for later wiring.
block_end_values: snapshots per block end to materialize predecessor values (dominance-safe).
finalize_phis(): wires incoming edges for declared PHIs; when MIR13 runs, it creates PHIs on the fly to recover SSA.
Resolver.resolve_i64():
- single-pred: take predecessor end value;
- multi-pred + declared PHI: reuse the placeholder at the block head;
- multi-pred + no PHI: synthesize a localization PHI at the current block head (MIR13 compatibility);
- avoids reusing non-dominating vmap values across blocks.

Bridge/Builder (JSON v0) Behavior

MIR14 (default): If/Loop/Try placements emit PHIs up front; loop latches, break/continue, and structured joins have explicit incoming pairs.
MIR13 (fallback): Merges are performed with edge copies (merge_var_maps). Use only when reproducing historical issues.

Testing (v2)

Integration suite (LLVM harness/PHI invariants):
- tools/smokes/v2/run.sh --profile integration
Bridge/PyVM の検証は v2 スイートに統合（必要に応じてフィルタを使用）

How to Force PHI-off (MIR13 fallback)

Set: NYASH_MIR_NO_PHI=1 NYASH_VERIFY_ALLOW_NO_PHI=1
Run integration: tools/smokes/v2/run.sh --profile integration
Label the run as legacy in CURRENT_TASK.md if results inform shared debugging.

Known Limitations (current)

MIR13 no longer receives new feature work; expect missing coverage for recent LoopForm updates.
PHI-on is the supported path. MIR13 bugs are fixed only when they block diagnostics.

2.8 KiB Raw Blame History Unescape Escape

2.8 KiB

Raw Blame History