Myth: Compilers optimizing based on undefined behavior is one of the biggest real world problems with C/C++. It’s actually nowhere near.
-
-
now compare a security problem caused by a use-after-free, which is something well understood vs a security problem caused by an undefined behavior that happens somewhere silently because you upgraded your toolchain
-
I agree that the latter is harder to debug, but the former has more real world impact simply because it occurs so much more frequently.
- 6 more replies
New conversation -
-
-
In a sense, not having -fsanitize=undefined -fsanitize-trap=undefined enabled by default is a compiler optimization. Still no way to even get close to meaningful bounds / temporal safety with either Clang or GCC even if willing to pay a 3x performance / memory usage cost though.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.