On Mon, Aug 26, 2013 at 9:32 AM, Jan Hubicka <hubi...@ucw.cz> wrote: >> On Mon, Aug 26, 2013 at 9:00 AM, Jan Hubicka <hubi...@ucw.cz> wrote: >> >> On Mon, Aug 26, 2013 at 7:24 AM, Jan Hubicka <hubi...@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? > > configure --with-build-config=bootstrap-lto .
I got this part. The question I asked relates to the when you said "then add -fdump-tree-all into the final link command line options." > You need plugin enabled buinutils for that. ah. > I think there however should be a lot easier way to reproduce it by just > dropping some really > large source file. Here LTO only runs the backend on very many functions. > > Honza I think the problem is in tree gimple dumpers. -- Gaby
