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 middle-end/56113] out of memory when compiling a function with many goto labels (50k > )
Date: Wed, 30 Jan 2013 14:38:00 -0000 [thread overview]
Message-ID: <bug-56113-4-PqPVjV3rPa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56113-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56113
--- Comment #16 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-30 14:38:29 UTC ---
The following (old!?) idea helps though:
Index: gcc/tree-ssa-loop-manip.c
===================================================================
--- gcc/tree-ssa-loop-manip.c (revision 195574)
+++ gcc/tree-ssa-loop-manip.c (working copy)
@@ -536,7 +536,7 @@ rewrite_into_loop_closed_ssa (bitmap cha
/* Fix up all the names found to be used outside their original
loops. */
- update_ssa (TODO_update_ssa);
+ update_ssa (TODO_update_ssa_no_phi);
}
/* Check invariants of the loop closed ssa form for the USE in BB. */
why would adding a copy on an edge (thus a new def) require us to insert
new PHI nodes? With that patch:
tree SSA incremental : 0.06 ( 0%) usr
TOTAL : 46.36
Of course I must not remember sth here ...
next prev parent reply other threads:[~2013-01-30 14:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 20:37 [Bug c/56113] New: " aixer77 at gmail dot com
2013-01-25 20:39 ` [Bug c/56113] " aixer77 at gmail dot com
2013-01-26 15:29 ` [Bug middle-end/56113] " rguenth at gcc dot gnu.org
2013-01-26 15:40 ` aixer77 at gmail dot com
2013-01-27 0:17 ` steven at gcc dot gnu.org
2013-01-27 11:24 ` steven at gcc dot gnu.org
2013-01-27 13:27 ` steven at gcc dot gnu.org
2013-01-28 9:45 ` rguenth at gcc dot gnu.org
2013-01-28 10:05 ` rguenth at gcc dot gnu.org
2013-01-28 23:35 ` steven at gcc dot gnu.org
2013-01-29 9:52 ` rguenther at suse dot de
2013-01-29 13:07 ` rguenth at gcc dot gnu.org
2013-01-29 14:23 ` rguenth at gcc dot gnu.org
2013-01-29 14:24 ` rguenth at gcc dot gnu.org
2013-01-29 15:38 ` rguenth at gcc dot gnu.org
2013-01-30 13:50 ` rguenth at gcc dot gnu.org
2013-01-30 14:38 ` rguenth at gcc dot gnu.org [this message]
2013-01-30 15:41 ` rguenth at gcc dot gnu.org
2013-01-31 10:13 ` rguenth at gcc dot gnu.org
2013-01-31 16:37 ` rguenth at gcc dot gnu.org
2013-01-31 16:53 ` rguenth at gcc dot gnu.org
2013-01-31 19:56 ` steven at gcc dot gnu.org
2013-01-31 20:16 ` steven at gcc dot gnu.org
2013-01-31 22:51 ` steven at gcc dot gnu.org
2013-01-31 23:23 ` steven at gcc dot gnu.org
2013-02-01 8:48 ` rguenther at suse dot de
2013-02-01 10:10 ` rguenth at gcc dot gnu.org
2013-02-01 12:39 ` rguenth at gcc dot gnu.org
2013-02-04 9:30 ` rguenth at gcc dot gnu.org
2013-03-06 10:54 ` [Bug c/56113] " steven at gcc dot gnu.org
2013-03-18 8:48 ` rguenth at gcc dot gnu.org
2013-03-18 10:02 ` rguenth at gcc dot gnu.org
2013-04-08 8:37 ` [Bug middle-end/56113] " rguenth at gcc dot gnu.org
2023-05-04 9:29 ` [Bug c/56113] " rguenth at gcc dot gnu.org
2023-05-04 10:02 ` rguenth at gcc dot gnu.org
2023-05-04 10:54 ` 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-56113-4-PqPVjV3rPa@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: link
Be 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).