Files
BFM-decomp/docs
Drew T 92c001ea8c docs(cookbook): §428a — the fence<->over-merge coupling (agent-measured, flagged not-yet-byte-proven)
A volatile __asm__ barrier is a scheduling AND allocation event, so on a function whose
residual is allocation-shaped every fence that kills the double-hop re-enables a
cross-jump over-merge. Two residuals in tension, which is why ~20 variants across two
attempts never converged. §428's UID-based barrier is the predicted resolution because
it changes no liveness; the escalation now running is the test.

Flagged explicitly as one agent's report, not a byte-proof (R14).
2026-09-02 12:26:01 -06:00
..