Whole program optimization and functions-only-called-once.

[Toon Moene]

Jan Hubicka wrote:

 > I wrote:

>> but it was nice to see the link  
>> time optimization of the largest executable being terminated by the OOM  
>> killer (after 10 minutes of CPU time, when reaching 12.5 Gbytes of 
>> memory).
>>
>> At least it gives the impression that some real work is put into  
>> optimizing our code :-)
> 
> :) It would be nice to know what caused the OOM.  Is just one of passes exploding
> on presence of very large bodies?

I'll try to figure this out over the weekend (sorry, don't have more 
spare time).

It's most probably a single pass, because the memory requirements kept 
creeping up to 12.5 Gbytes from 10, slowly increasing all the time over 
several minutes.

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/
Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html