public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114578] New: [13/14 Regression] memory hog, virtual memory exhausted, building a c++ file on arm-linux-gnueabihf Date: Thu, 04 Apr 2024 07:37:27 +0000 [thread overview] Message-ID: <bug-114578-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114578 Bug ID: 114578 Summary: [13/14 Regression] memory hog, virtual memory exhausted, building a c++ file on arm-linux-gnueabihf Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: doko at gcc dot gnu.org Target Milestone: --- seen with the 13 branch and trunk, building on arm-linux-gnueabihf. $ g++ -g -O0 -fstack-protector-strong -fno-stack-clash-protection -fno-exceptions -std=gnu++17 -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -c qrc_assets.ii virtual memory exhausted: Cannot allocate memory the gcc-12 branch is able to build that with -g -O2. preprocessed source (120MB uncompressed) at https://people.debian.org/~doko/tmp/qrc_assets.ii.xz
next reply other threads:[~2024-04-04 7:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-04 7:37 doko at gcc dot gnu.org [this message] 2024-04-04 21:03 ` [Bug target/114578] " pinskia at gcc dot gnu.org 2024-04-04 21:06 ` [Bug c++/114578] " pinskia at gcc dot gnu.org 2024-04-04 21:09 ` pinskia at gcc dot gnu.org 2024-04-04 21:10 ` pinskia at gcc dot gnu.org 2024-04-04 21:17 ` pinskia at gcc dot gnu.org 2024-04-14 5:22 ` pinskia at gcc dot gnu.org 2024-05-21 9:19 ` [Bug c++/114578] [13/14/15 " jakub 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-114578-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).