[Bug c/58454] Potentially wrong(or at least weird/inconsistent) code generation with -O2 -fno-strict-overflow
rguenth at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Wed Sep 18 08:45:00 GMT 2013
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58454
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-09-18
CC| |iant at google dot com
Ever confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
-fno-strict-overflow should have never been added because it certainly does not
disable all use of undefined signed overflow behavior. Which makes it kind-of
useless.
Ian, the documentation of -fno-strict-overflow suggests that the compiler
will not rely on signed overflow not happening. That's not true, so this
is definitely a documentation bug.
More information about the Gcc-bugs
mailing list