This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Whole program optimization and functions-only-called-once.
On Wed, Nov 18, 2009 at 9:50 PM, Toon Moene <toon@moene.org> wrote:
> 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.
The obvious bet is anything using DF on the RTL side or var-tracking if
you enabled -g.
Richard.