What Every C Programmer Should Know About Undefined Behavior #⅔¶
Lattner, C. (2011). What Every C Programmer Should Know About Undefined Behavior #2/3.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Compiler Optimization Pass
- The canonical case is optimizing around undefined behaviour: the pass may legally assume a program contains none, and when the program in fact does, an "equivalence-preserving" rewrite can change its observable behaviour.
This sourceExplains that C and C++ optimizers may assume undefined behavior does not occur and that optimization based on that assumption can produce surprising changed behavior in buggy programs.
- The canonical case is optimizing around undefined behaviour: the pass may legally assume a program contains none, and when the program in fact does, an "equivalence-preserving" rewrite can change its observable behaviour.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:7e1c469ebc97 · see in the full table