Compiler UB gotchas mean your spec itself needs to be proven UB-free
ezyang · x · 2026-11-09
Even when reusing a programming language as the spec language, C compilers' famous "non-bug" behavior bites: UB after a condition lets the compiler assume the condition must always be false. ezyang's conclusion: better prove your spec has no UB, or low-level compilation semantics can silently undermine the verification result.
More from coding & agent
- Team's AI agent fixes 40 of 41 user-reported issues in a single weekend — julianweisser · 2026-11-09
- HEELO Harness Framework Lifts Terminal-Bench Resolution from 37.3% to 55.5% — Haibo Jin · 2026-11-09
- NVIDIA's AgentBaton: Well-Timed Strong-to-Weak Model Handoffs Slash Agent Costs — nvidia · 2026-11-09
- FrontierCS 2 update: Claude Sonnet 5.5 beats reference on 50% of tasks, reward hacks published — ajratner · 2026-11-09
- "Being technical" now means having the patience to ask Claude until you get it — brandon_galang · 2026-11-09
- Together AI: leaderboards are for shortlisting, your production traffic is the real benchmark — togethercompute · 2026-11-09