public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114480] g++: internal compiler error: Segmentation fault signal terminated program cc1plus Date: Wed, 03 Apr 2024 06:57:09 +0000 [thread overview] Message-ID: <bug-114480-4-xGs0U8PwGX@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 #17 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:e7b7188b1cf8c174f0e890d4ac279ff480b51043 commit r14-9767-ge7b7188b1cf8c174f0e890d4ac279ff480b51043 Author: Richard Biener <rguenther@suse.de> Date: Tue Apr 2 12:31:04 2024 +0200 tree-optimization/114557 - reduce ehcleanup peak memory use The following reduces peak memory use for the PR114480 testcase at -O1 which is almost exclusively spent by the ehcleanup pass in allocating PHI nodes. The free_phinodes cache we maintain isn't very effective since it has effectively two slots, one for 4 and one for 9 argument PHIs and it is only ever used for allocations up to 9 arguments but we put all larger PHIs in the 9 argument bucket. This proves uneffective resulting in much garbage to be kept when incrementally growing PHI nodes by edge redirection. The mitigation is to rely on the GC freelist for larger sizes and thus immediately return all larger bucket sized PHIs to it via ggc_free. This reduces the peak memory use from 19.8GB to 11.3GB and compile-time from 359s to 168s. PR tree-optimization/114557 PR tree-optimization/114480 * tree-phinodes.cc (release_phi_node): Return PHIs from allocation buckets not covered by free_phinodes to GC. (remove_phi_node): Release the PHI LHS before freeing the PHI node. * tree-vect-loop.cc (vectorizable_live_operation): Get PHI lhs before releasing it.
next prev parent reply other threads:[~2024-04-03 6:57 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 [this message] 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 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-xGs0U8PwGX@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).