By-Value Boundary Trio
Algorithms & DataThree lanes plot stage outputs, with a steady baseline beneath each lane representing the caller's reread of its own original record.
Self-running — no controller input required.
Verify fidelity checks the recorded result against 0x4FAB.
Source byvaledge.cbyvaledge.h in wbniv/llvm-mos-65816
What you see
Three lanes plot stage outputs, with a steady baseline beneath each lane representing the caller's reread of its own original record.
The defect this ROM exposed
The original five-byte update stage put three ordinary stores of mixed widths through one uint16_t *, with a call between them. At -O1 and above the register allocator ran out of registers. This is a real upstream MOS allocation failure, not a 65816-only feature gap: the minimal shape reproduces with pristine upstream llc and the pristine MOS data layout on mos6502.
The ROM keeps the ABI question under test but does not disguise the compiler limitation. Its shipped gate moves the offending libcall out of the five-byte stage rather than weakening the caller/callee copy checks. That is a scoped workaround, not a claimed allocator repair; the upstream issue contains the reduced source and the configuration matrix.
What is checked
Four-byte records use direct scalar arguments; five-byte records use indirect arguments. Each callee mutates its parameter, and the caller checks that its own value is unchanged. A declared 33-bit bitfield record occupies five whole bytes on MOS. The checked ROM folds all three stages and the caller rereads into 0x4FAB, so an ABI copy regression remains observable on both published emulator paths.
Compiler stress-test #154. The downloadable ROM and browser player use the same verified artifact.