http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53265
--- Comment #10 from Alexander Monakov <amonakov at gcc dot gnu.org> 2013-03-11 16:15:36 UTC --- (In reply to comment #8) > Not sure about the warning wording What about (... "iteration %E invokes undefined behavior", max)? > plus no idea how to call the warning option (-Wnum-loop-iterations, > -Wundefined-behavior-in-loop, something else?) Can it be -Waggressive-loop-optimizations to follow existing pairs of -{W,fno-}strict-{aliasing,overflow} for the recently added -fno-aggressive-loop-optimizations?