public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109794] New: Compile time hog when building chromium on aarch64-unknown-linux-gnu Date: Tue, 09 May 2023 20:27:12 +0000 [thread overview] Message-ID: <bug-109794-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109794 Bug ID: 109794 Summary: Compile time hog when building chromium on aarch64-unknown-linux-gnu Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: compile-time-hog, memory-hog Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org Target Milestone: --- Created attachment 55034 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55034&action=edit evaluate_prg_hwy.ii.xz Originally reported downstream in Gentoo at https://bugs.gentoo.org/905818. With GCC 12 (12.2.1 20230505), this has reached over 30GB memory usage before I killed it. I've asked the reporter for preprocessed source for 13 as well. Reproduces for me with 12 using: ``` g++-12 -c evaluate_prg_hwy.ii -std=c++20 -O2 ``` but even -O0 is enough.
next reply other threads:[~2023-05-09 20:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-09 20:27 sjames at gcc dot gnu.org [this message] 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 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@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: linkBe 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).