Re:Boringcc: Proposal for a C compiler for secure software
by ProblemFactory on Tuesday December 22, 2015 @10:50AM
(#10778363)
A lot of undefined behaviour cannot be identified at compile time. For example, adding two signed integers is undefined if it overflows, but perfectly well defined if it does not.
A safe compiler will have to add checks to guard against undefined behaviour happening at runtime.
So sub-optimal but predictable and safe code given that you change the preference bit to safety over speed.