http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52316
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-20
15:07:27 UTC ---
Is it sufficiently common to do something that insane though?
We optimize away the dead code in there of course, but the problem is that it
uses a floating point iterator. I guess our number of iterations analysis just
gives up when the IV is floating, here for known compile time constant init
value and condition operand if both values are sufficiently small we could
compute the number of iterations anyway, but as soon as adding 1 to a floating
point value doesn't change it, for IEEE single when the value is 16777216.0f,
you end up with an endless loop, and that should be honored even for -Ofast.
