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

[Jan Hubicka]

> Rafael Espindola wrote:
>
>>> Done. You will very likely hit another bug when using a resolution
>>> file. I am testing a patch for it.
>>
>> Done. It should now have only the old bugs :-)
>
> Yep, that worked.  Inlining all functions-only-called-once doesn't get  
> any speed up however (on the contrary). 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?

Honza
>
> Kind regards,
>
> -- 
> 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