~/talk

Undefined Behavior is Not an Error

Talkat CppCon 2018 · 2018-09-23..09-28· [c-and-cpp]

speakers

name:Barbara Geller

links:none on file

name:Ansel Sermersheim

links:none on file

resources

video:https://youtu.be/XEXpwis_deQ

slides:none on file

summary

Core claim: undefined behavior is not an error — the compiler may legally treat UB as “code not present,” leading to surprising results. Real examples: a missing return jumps into the next function, an out‑of‑bounds operator[] lets an optimizer remove loop bodies (output becomes empty), and signed integer overflow lets clang replace a loop with a multiply/divide. Fixes: rewrite code or use safer patterns (version 3 used compile‑time counter, constexpr and recursive templates and avoids UB). Tools: sanitizers, Coverity, clang static analyzer, valgrind, godbolt and multiple compilers/flags.

AI-written summary · about

chapters (13)

related talks