Retry-On-Fault Ladder
Algorithms & DataEach column climbs to its recorded call depth. A fault snaps the column back to the baseline and leaves a short record of the attempt.
Self-running — no controller input required.
Verify fidelity checks the recorded result against 0x3388.
Source retryjmp.cretryjmp.h in wbniv/llvm-mos-65816
What you see
Each column climbs to its recorded call depth. A fault snaps the column back to the baseline and leaves a short record of the attempt.
The defect this ROM exposed
This ROM found a distinct +mos-xy16 wrong-code failure while materialising a spill-slot address. Frame-index elimination reused the live Imag16 pair that held the value about to be stored; the following 16-bit indexed store wrote the index expression instead of that value. It is not the benign verifier-only undef-lane diagnostic: the machine code changes the program's result.
The preserved observation is host/default/+mos-a16 = 0x3388, while +mos-xy16 produced 0x82D4. That is evidence of an open backend defect, not a license to weaken the test. The source, reduction, assembly, and exact configuration remain in the linked compiler investigation.
What is checked
The same setjmp site is re-entered 24 times from different recursive depths. The result sequence covers stack restoration, saved registers, and values retained across each retry. The public ROM is the current verified artifact, while the discovery record preserves the failing native-width baseline and the page intentionally makes no claim that a backend repair has been established.
Compiler stress-test #118. The downloadable ROM and browser player use the same verified artifact.