Re: secondary expansion changes
Paul Smith <[email protected]>
| Newsgroups | gmane.comp.gnu.make.devel |
|---|---|
| Organization | GNU's Not Unix! |
| Message-ID | <[email protected]> |
On Mon, 2009-09-28 at 11:53 +0200, Boris Kolpackov wrote: > Boris Kolpackov <[email protected]> writes: > > > http://www.codesynthesis.com/~boris/tmp/make-valgrind.log > > Here is another one, for today's cvs: > > http://www.codesynthesis.com/~boris/tmp/make-valgrind-1.log Ah, this looks much better. You don't need to use the --still-reachable=yes flag; make makes no attempt to clean up all memory that it has allocated before it exits. This is a performance feature, not a bug :-). I ran a build of glibc and the memory profile looks better there too. I'm still interested in any other information you have on where the huge amount of allocated/then freed memory is in your environment. Also, if you have comparisons to older versions of make and their memory profile (if your environment can build with them). Thanks! -- ------------------------------------------------------------------------------- Paul D. Smith <[email protected]> Find some GNU make tips at: http://www.gnu.org http://make.mad-scientist.net "Please remain calm...I may be mad, but I am a professional." --Mad Scientist