Interpreting -fmem-report

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

I am interested in -fmem-report to help diagnose an issue
with memory thrashing during a parallel build.  Ech separate
compilation if and of itself is not enough to cause the thrash,
but when they're added up over a parallel compile, things go
south.

So I want to collect total memory usage of GCC during a
compilation and then sum them over the last 16 or so GCC
invocations we have.  But I am having a hard time figuring
out the total usage.  I see nothing obvious.  Any hints?

Thanks,

Tom



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux