I've also seen gcc go beserk and start taking up over 150 MB of memory on a pretty simple compile 'cause it got confused and take forever to compile. Last time I saw this happen, I waited a half-hour to see if it would eventually compile. Meanwhile, the memory usage was pegged at 99% or so. Eventually I just killed the process. With -O2, the same file took 10 seconds to compile.
J Aaron Bannert wrote: > On Fri, Apr 19, 2002 at 03:50:16PM +0200, Sebastian Bergmann wrote: >> Yasuo Ohgaki wrote: >> > Any objection for changing -O2 -> -O3 when >> > --enable-inline-optimization is used? (when GCC is used) >> >> What happened to the plan of making --enable-inline-optimization the >> default? > > Is making these kinds of optimizations by default such a good idea? I've > seen many a broken gcc install produce incorrect binaries with the larger > -O optimizations turned on (unfortunately). > > -aaron -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
