public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109794] Massive memory usage when building chromium on aarch64-unknown-linux-gnu
Date: Tue, 09 May 2023 23:40:56 +0000	[thread overview]
Message-ID: <bug-109794-4-iU3xlsbayL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109794-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109794

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
-O0:
 LRA non-specific                   :  33.12 ( 20%)   0.06 (  1%)  33.15 ( 19%)
  279M ( 25%)
 LRA virtuals elimination           :   2.08 (  1%)   0.00 (  0%)   2.08 (  1%)
   18M (  2%)
 LRA reload inheritance             :   4.18 (  2%)   0.00 (  0%)   4.15 (  2%)
   36k (  0%)
 LRA create live ranges             :  11.41 (  7%)   0.00 (  0%)  11.45 (  6%)
   28M (  2%)
 LRA hard reg assignment            :  37.83 ( 22%)   0.04 (  0%)  37.86 ( 21%)
    0  (  0%)

  parent reply	other threads:[~2023-05-09 23:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 20:27 [Bug c++/109794] New: Compile time hog " sjames at gcc dot gnu.org
2023-05-09 20:28 ` [Bug c++/109794] Massive memory usage " sjames at gcc dot gnu.org
2023-05-09 20:30 ` pinskia at gcc dot gnu.org
2023-05-09 20:36 ` [Bug target/109794] " sjames at gcc dot gnu.org
2023-05-09 23:31 ` pinskia at gcc dot gnu.org
2023-05-09 23:33 ` pinskia at gcc dot gnu.org
2023-05-09 23:40 ` pinskia at gcc dot gnu.org [this message]
2023-05-09 23:45 ` pinskia at gcc dot gnu.org
2023-05-09 23:47 ` pinskia at gcc dot gnu.org

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=bug-109794-4-iU3xlsbayL@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).