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/54489] New: tree FRE uses an excessive amount of memory Date: Wed, 05 Sep 2012 10:28:00 -0000 [thread overview] Message-ID: <bug-54489-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54489 Bug #: 54489 Summary: tree FRE uses an excessive amount of memory Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: memory-hog Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: rguenth@gcc.gnu.org FRE can use an excessive amount of memory for storing AVAIL_OUT bitmaps needed for leader finding in eliminate (). The testcase of PR46590 does not fit into 4GB of memory because of this. The root cause is: /* Initially, the set of available values in BLOCK is that of its immediate dominator. */ dom = get_immediate_dominator (CDI_DOMINATORS, block); if (dom) bitmap_set_copy (AVAIL_OUT (block), AVAIL_OUT (dom)); basically accumulating at least all dominating SSA defs with different value-number in each basic-block. Instead of applying surgery to FRE in tree-ssa-pre.c FRE should be split out and unify eliminate () and avail computation in a dominator walk which would avoid keeping all AVAIL_OUT bitmaps live at a time.
next reply other threads:[~2012-09-05 10:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-05 10:28 rguenth at gcc dot gnu.org [this message] 2012-09-05 13:52 ` [Bug tree-optimization/54489] " rguenth at gcc dot gnu.org 2012-09-10 14:38 ` rguenth at gcc dot gnu.org 2012-09-12 14:46 ` rguenth at gcc dot gnu.org 2012-09-12 14:48 ` rguenth 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-54489-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).