This is the mail archive of the gcc-patches@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: Clean up pretty printers [18/n]


On Mon, Aug 26, 2013 at 9:00 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
>> On Mon, Aug 26, 2013 at 7:24 AM, Jan Hubicka <hubicka@ucw.cz> wrote:
>> > Hi,
>> > it seems to be couple weeks I am not able to compile big ltrans unit with -fdump-tree-all
>> > because the compiler eventually runs out of memory.  I think it is one of your patches
>> > introducing serious memory leak.  Can you, please, take a look on this? It makes my life
>> > harder - it is not fun to wait for 15 minutes for a dump and then see compiler to ICE...
>> >
>> > Thanks,
>> > Honza
>>
>>
>> The existing pretty printers have always had memory leaks, and
>> part of the work is to reduce that in fact :-(   For example, instead
>> of printing directly to the output buffer, many of them construct
>> a string for a given formatter, then send that string to the stream,
>> and that string may or may not be reclaimed.  Please give me
>> actionable instructions so I can reproduce your situation.
>
> I think it should be easiert to build with bootstrap-lto and then add -fdump-tree-all into
> the final link command line options.

modify ALL_LINKERFLAGS or BUILD_LINKERFLAGS?


> It seems to reproduce quite uniformlny and doesn't
> seem to be specific to my firefox builds I am doing right now…

I think I may have an idea about  which existing leak is making itself
noticed but I am looking for a (semi-)automatic way to regtest it.


>
> Thanks!
> Honza
>>
>> -- Gaby


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