http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58454
Ian Lance Taylor <ian at airs dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian at airs dot com --- Comment #4 from Ian Lance Taylor <ian at airs dot com> --- Richi, as you know, -fno-strict-overflow was added to prevent people from configuring GCC to make -fwrapv the default. I know you hate the option but I continue to think that adding was the right tactical move at the time. We can't just ignore the world outside the compiler development community. It's true that -fno-strict-overflow does not apply to loop optimizations, which are covered by -fno-aggressive-loop-optimizations. I agree that that is a doc omission.