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 tree-optimization/114557] ehcleanup cleanup_empty_eh_merge_phis eats a lot of memory Date: Tue, 02 Apr 2024 10:30:01 +0000 [thread overview] Message-ID: <bug-114557-4-Rteavp2UMk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114557-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114557 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- The free_phinodes buckets itself could better use the ->next chain of the gimple stmts rather than a (re-allocated) GC vector. Given the current bucket structure a single chain for the 4-argument case might be good enough. Otherwise hooking into the GC special sizes array might be worthwhile. Note that ggc_free()ing all PHIs (and thus using the GC allocator freelist which has its own issues) is a tiny bit faster than keeping the pool for at least the testcase at hand.
next prev parent reply other threads:[~2024-04-02 10:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-02 8:59 [Bug tree-optimization/114557] New: " rguenth at gcc dot gnu.org 2024-04-02 9:56 ` [Bug tree-optimization/114557] " rguenth at gcc dot gnu.org 2024-04-02 10:30 ` rguenth at gcc dot gnu.org [this message] 2024-04-03 6:57 ` 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-114557-4-Rteavp2UMk@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).