This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Memory usage statistics
- To: Brad Lucier <lucier at math dot purdue dot edu>
- Subject: Re: Memory usage statistics
- From: "Zack Weinberg" <zackw at stanford dot edu>
- Date: Thu, 30 Nov 2000 14:28:49 -0800
- Cc: gcc at gcc dot gnu dot org
- References: <200011301901.eAUJ1d503859@polya.math.purdue.edu>
On Thu, Nov 30, 2000 at 02:01:39PM -0500, Brad Lucier wrote:
> I have a question:
>
> How can I discover in which passes gcc is using the most memory?
Right now, there really isn't a way to do that. You can use -Q and
grep out the {GC x -> y} bits, but that will only tell you which
*function* uses the most memory. -fmem-report will tell you how much
memory was allocated permanently over the entire compilation, again
not what you want.
I've been meaning to augment -fmem-report so it reports peak
allocation and after-GC allocation at least as often as each full GC
run. Per pass wouldn't be that much harder, particularly if you don't
mind running the garbage collector more than is strictly necessary.
I won't have time to do it anytime soon, though. Feel free to beat me
to it :)
zw