On Sun, 17 Feb 2013, Gerald Pfeifer wrote: > On Thu, 31 Jan 2013, Richard Biener wrote: > > +<p>GCC now uses more a aggressive analysis to derive an upper bound for > > I think "a " should be omitted here.
Yes, that was fixed before commit. > > +the number of iterations of loops using constraints imposed by language > > +standards. This may cause non-conforming programs to no longer work as > > +expected, such as SPEC CPU 2006 464.h264ref and 416.gamess. A new > > +option, <code>-fno-aggressive-loop-optimizations</code>, was added > > +to disable this aggressive analysis.</p> > > Personally I would reduce aggressiveness and omit "aggressive" in > the last line above. :-) Heh ... as you like ;) Richard.
