>Why has nobody pushed for marking key sections of code with "don't optimise away" flags? The issue isn't that certain code is optimized away. That's just a sy

>Why has nobody pushed for marking key sections of code with "don't optimise away" flags? The issue isn't that certain code is optimized away. That's just a symptom of the fact that it's incorrect C code relying on the way a specific system treats undefined behavior. Checking for overflow can be done with correct C code that doesn't rely on undefined behavior, so putting in a hack that lets incorrect C work in some situations does not seem like the right answer.