public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114480] [12/13/14 Regression] g++: internal compiler error: Segmentation fault signal terminated program cc1plus Date: Tue, 09 Apr 2024 11:39:50 +0000 [thread overview] Message-ID: <bug-114480-4-Gf8SBlnJZ3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114480-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114480 --- Comment #30 from Richard Biener <rguenth at gcc dot gnu.org> --- Temporarily memory goes to out-of-SSA computing liveness (2GB), after RTL expansion it drops to ~900MB peak again. Then df-init-at-O0 bumps to 1.3GB and then IRA goes all the way to >3GB. We're using lra_simple_p because num_used_regs is 343033 and last_basic_block is 117142. It's df_analyze () which brings memory usage to 2.8GB. After ira_build () it's 3.4GB. There's 1.5GB used in LR problem data bitmaps, we are not separating the local computed bitmaps from the global solution (the DF machinery doesn't have a separate "local compute" free, possibly the finalize hook can be used for this). Though the local compute bitmaps only use around 20MB. The DF bitmap obstack itself is quite small as well. Of course it's all because we fail to implement the initializers EH cleanup in a more sensible way. Complete "elements" could be processed in a loop over the containers elements while only a single partially under-construction element would need to be handled "inline".
next prev parent reply other threads:[~2024-04-09 11:39 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-26 11:40 [Bug c++/114480] New: " douglas.boffey at gmail dot com 2024-03-26 11:42 ` [Bug c++/114480] " douglas.boffey at gmail dot com 2024-03-26 11:46 ` pinskia at gcc dot gnu.org 2024-03-26 11:46 ` pinskia at gcc dot gnu.org 2024-03-26 11:51 ` douglas.boffey at gmail dot com 2024-03-26 12:05 ` pinskia at gcc dot gnu.org 2024-03-26 12:15 ` pinskia at gcc dot gnu.org 2024-03-26 12:26 ` pinskia at gcc dot gnu.org 2024-03-26 12:26 ` pinskia at gcc dot gnu.org 2024-03-26 12:31 ` douglas.boffey at gmail dot com 2024-03-26 12:41 ` redi at gcc dot gnu.org 2024-03-27 8:28 ` rguenth at gcc dot gnu.org 2024-03-27 19:49 ` vmakarov at gcc dot gnu.org 2024-03-28 8:17 ` cvs-commit at gcc dot gnu.org 2024-03-28 8:44 ` rguenth at gcc dot gnu.org 2024-03-28 10:12 ` rguenth at gcc dot gnu.org 2024-03-28 10:39 ` rguenth at gcc dot gnu.org 2024-04-02 13:28 ` rguenth at gcc dot gnu.org 2024-04-03 6:57 ` cvs-commit at gcc dot gnu.org 2024-04-03 11:47 ` rguenth at gcc dot gnu.org 2024-04-04 9:42 ` rguenth at gcc dot gnu.org 2024-04-04 18:41 ` amonakov at gcc dot gnu.org 2024-04-05 15:35 ` amonakov at gcc dot gnu.org 2024-04-08 9:46 ` rguenth at gcc dot gnu.org 2024-04-08 9:50 ` douglas.boffey at gmail dot com 2024-04-08 9:54 ` rguenther at suse dot de 2024-04-08 12:32 ` douglas.boffey at gmail dot com 2024-04-08 13:07 ` rguenther at suse dot de 2024-04-08 13:22 ` [Bug c++/114480] [12/13/14 Regression " rguenth at gcc dot gnu.org 2024-04-08 13:37 ` [Bug c++/114480] [12/13/14 Regression] " rguenth at gcc dot gnu.org 2024-04-09 7:51 ` rguenth at gcc dot gnu.org 2024-04-09 11:39 ` rguenth at gcc dot gnu.org [this message] 2024-05-14 13:41 ` [Bug c++/114480] [12/13/14/15 " rguenth at gcc dot gnu.org 2024-05-17 12:29 ` cvs-commit 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-114480-4-Gf8SBlnJZ3@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).