public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Kacvinsky <tkacvins@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Interpreting -fmem-report
Date: Tue, 4 Jan 2022 15:08:53 -0500	[thread overview]
Message-ID: <CAG_eJLd6qbwY+583poJVW4AbPd+tWa+qEfRBWOBYjsfj7LoRDg@mail.gmail.com> (raw)

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

             reply	other threads:[~2022-01-04 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 20:08 Tom Kacvinsky [this message]
2022-01-04 21:09 ` Jonathan Wakely
2022-01-04 23:32   ` Tom Kacvinsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAG_eJLd6qbwY+583poJVW4AbPd+tWa+qEfRBWOBYjsfj7LoRDg@mail.gmail.com \
    --to=tkacvins@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).