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 lto/51635] [4.7 regression] ICE in in dwarf2out_finish, at dwarf2out.c:22494 when building Firefox's libxul
Date: Wed, 21 Dec 2011 16:09:00 -0000 [thread overview]
Message-ID: <bug-51635-4-Q0fNGwC9WE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51635-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51635
--- Comment #23 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-12-21 16:01:30 UTC ---
Another fun (well ...) patch that is worth trying is
Index: gcc/gimple.c
===================================================================
--- gcc/gimple.c (revision 182590)
+++ gcc/gimple.c (working copy)
@@ -4488,16 +4488,7 @@ gimple_register_type_1 (tree t, bool reg
tree
gimple_register_type (tree t)
{
- gcc_assert (TYPE_P (t));
-
- if (!gimple_type_leader)
- gimple_type_leader = ggc_alloc_cleared_vec_gimple_type_leader_entry_s
- (GIMPLE_TYPE_LEADER_SIZE);
-
- if (gimple_types == NULL)
- gimple_types = htab_create_ggc (16381, gimple_type_hash, gimple_type_eq,
0);
-
- return gimple_register_type_1 (t, false);
+ return t;
}
/* The TYPE_CANONICAL merging machinery. It should closely resemble
where you need to configure with --disable-werror (because of now unused
functions in gimple.c). The above will simply disable all type merging
and thus may in theory increase memory usage a lot (I think so more for
ltrans stage than wpa stage, it also may increase ltrans file size a lot).
It also probably increases the size of the emitted debug information.
next prev parent reply other threads:[~2011-12-21 16:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 12:06 [Bug lto/51635] New: " markus at trippelsdorf dot de
2011-12-20 12:14 ` [Bug lto/51635] " rguenth at gcc dot gnu.org
2011-12-20 12:26 ` rguenth at gcc dot gnu.org
2011-12-20 14:42 ` rguenth at gcc dot gnu.org
2011-12-20 15:15 ` rguenth at gcc dot gnu.org
2011-12-20 15:38 ` markus at trippelsdorf dot de
2011-12-20 15:40 ` rguenther at suse dot de
2011-12-20 15:49 ` rguenther at suse dot de
2011-12-20 18:12 ` markus at trippelsdorf dot de
2011-12-21 9:38 ` rguenth at gcc dot gnu.org
2011-12-21 9:48 ` markus at trippelsdorf dot de
2011-12-21 11:04 ` rguenth at gcc dot gnu.org
2011-12-21 11:17 ` rguenth at gcc dot gnu.org
2011-12-21 12:58 ` markus at trippelsdorf dot de
2011-12-21 12:59 ` rguenth at gcc dot gnu.org
2011-12-21 13:01 ` rguenth at gcc dot gnu.org
2011-12-21 13:48 ` rguenth at gcc dot gnu.org
2011-12-21 14:01 ` markus at trippelsdorf dot de
2011-12-21 14:08 ` rguenther at suse dot de
2011-12-21 15:07 ` rguenth at gcc dot gnu.org
2011-12-21 15:11 ` rguenth at gcc dot gnu.org
2011-12-21 15:51 ` markus at trippelsdorf dot de
2011-12-21 16:02 ` rguenther at suse dot de
2011-12-21 16:09 ` rguenth at gcc dot gnu.org [this message]
2011-12-21 16:44 ` matz at gcc dot gnu.org
2011-12-22 10:15 ` markus at trippelsdorf dot de
2012-01-03 11:34 ` [Bug lto/51635] LTO should not merge (type) decls with different locations 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-51635-4-Q0fNGwC9WE@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).