Compilers Are Translators with Taste

A compiler is not a neutral pipeline — it is a translator with taste, and every optimization is a preference about what your program should mean.

We chased size in Nightbind’s WASM combat sim and -C opt-level=z rewrote an overflow check the debug build still exercised. Same source, different binaries, because LLVM decided the panic path was dead under release assumptions. QA caught it only because a stress test ran against release artifacts — the kind of gap teams skip when “it works on my machine” means debug.¹ Engineers who treat the compiler as a black box surrender decisions they never knew they were making: inlining thresholds, alias rules, undefined-behavior edges.

Read the assembly occasionally. Diff debug against release when behavior diverges. Two compilers given the same source will not produce equivalent binaries because they do not share preferences. The argument between your source and the backend is instructive.

Your compiler has opinions. Know what they are before they ship.

— JV · Dark Heart Labs.

LLVM Project documentation on undefined behavior and optimization — the canonical reminder that compilers may assume UB cannot happen and rewrite accordingly. ↩