[Bug regression/56844] Loop condition wrongly optimized from < to !=

jakub at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Thu Apr 4 16:43:00 GMT 2013


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56844

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-04-04 16:43:03 UTC ---
You can work around it in this case with -fno-aggressive-loop-optimizations,
though obviously it is much better to fix up the broken code.
The reason why we don't warn about this with -Waggressive-loop-optimizations is
that due to the && in the loop condition the loop doesn't have a single exit.



More information about the Gcc-bugs mailing list