2026-03-24 13:40:41 +00:00

542 B
Raw Blame History

Stress test outline (to add in PR7.9 or here if desired) • Build a bytecode program with a tight loop containing arithmetic + occasional YIELD and ensure: ◦ Under tiny budgets (1n cycles), pc progression is identical across runs. What I changed and why Open in editor ◦ Switches (simulated by alternating between two VMs) occur only ▪ immediately after step() completes, or ▪ when run_budget returns FrameSync. ◦ No observable state change occurs when forceswitching between two VMs midtick except at these safepoints.