This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: mainline "exploding"


> I do not have hard data yet, but it seems for C++ (see PR8361) for an
> example, even with  -O1 mainline started exploding in terms of memory
> consumption (and possibly compile time) over the weekend or so.
> 
> Any ideas?

This is probably related to increasing inlne limits :(
We now compile faster when unit-at-a-time is enabled at -O2:

hubicka@kampanus:/aux/hubicka/egcs/gcc/build/gcc$ time ./xgcc -B ./ -O1
generate-3.4.ii   -funit-at-a-time -S

real    0m45.663s
user    0m42.540s
sys     0m0.720s

I've sent patch containing rewrite of non-unit-at-a-time inlining
heuristics.  It reduces the compilation times at -O1 somewhat, but still
there is room for improvement as seen on other testcase from POOMA
library.  I am thinking about either decreasing the limits of overall
fucntion body growth at -O1 or doing kind of incremental version of
overall compilation unit growth limit.

Honza
> 
> Gerald


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]