From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Tom Kacvinsky <tkacvins@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Interpreting -fmem-report
Date: Tue, 4 Jan 2022 21:09:28 +0000 [thread overview]
Message-ID: <CAH6eHdRY7JFe8ccFPJDrbmzQ6sXc-_Eazb5eHJ+q4rA2X+yb-w@mail.gmail.com> (raw)
In-Reply-To: <CAG_eJLd6qbwY+583poJVW4AbPd+tWa+qEfRBWOBYjsfj7LoRDg@mail.gmail.com>
On Tue, 4 Jan 2022, 20:10 Tom Kacvinsky via Gcc-help, <gcc-help@gcc.gnu.org>
wrote:
> 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?
>
-ftime-report gives a simple total.
next prev parent reply other threads:[~2022-01-04 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 20:08 Tom Kacvinsky
2022-01-04 21:09 ` Jonathan Wakely [this message]
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=CAH6eHdRY7JFe8ccFPJDrbmzQ6sXc-_Eazb5eHJ+q4rA2X+yb-w@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tkacvins@gmail.com \
/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).