public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Interpreting -fmem-report
@ 2022-01-04 20:08 Tom Kacvinsky
  2022-01-04 21:09 ` Jonathan Wakely
  0 siblings, 1 reply; 3+ messages in thread
From: Tom Kacvinsky @ 2022-01-04 20:08 UTC (permalink / raw)
  To: gcc-help

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-01-04 23:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-04 20:08 Interpreting -fmem-report Tom Kacvinsky
2022-01-04 21:09 ` Jonathan Wakely
2022-01-04 23:32   ` Tom Kacvinsky

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).