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 c++/60553] segfault in gt_ggc_mx_lang_tree_node in Chromium with LTO
Date: Tue, 18 Mar 2014 11:00:00 -0000 [thread overview]
Message-ID: <bug-60553-4-fc6hI92mLt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60553-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60553
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Another idea would be (many next-variant walks in the call stack)
Index: lto/lto-tree.h
===================================================================
--- lto/lto-tree.h (revision 208615)
+++ lto/lto-tree.h (working copy)
@@ -48,7 +48,7 @@ enum lto_tree_node_structure_enum {
};
union GTY((desc ("lto_tree_node_structure (&%h)"),
- chain_next ("CODE_CONTAINS_STRUCT (TREE_CODE (&%h.generic),
TS_COMMON) ? ((union lang_tree_node *) TREE_CHAIN (&%h.generic)) : NULL")))
+ chain_next ("CODE_CONTAINS_STRUCT (TREE_CODE (&%h.generic),
TS_TYPE_COMMON) ? ((union lang_tree_node *) TYPE_NEXT_VARIANT (&%h.generic)) :
CODE_CONTAINS_STRUCT (TREE_CODE (&%h.generic), TS_COMMON) ? ((union
lang_tree_node *) TREE_CHAIN (&%h.generic)) : NULL")))
lang_tree_node
{
union tree_node GTY ((tag ("TS_LTO_GENERIC"),
next prev parent reply other threads:[~2014-03-18 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 14:54 [Bug c++/60553] New: " marxin.liska at gmail dot com
2014-03-17 15:23 ` [Bug c++/60553] " rguenth at gcc dot gnu.org
2014-03-17 15:45 ` marxin.liska at gmail dot com
2014-03-18 10:28 ` rguenth at gcc dot gnu.org
2014-03-18 11:00 ` rguenth at gcc dot gnu.org [this message]
2014-03-18 15:33 ` marxin.liska at gmail dot com
2014-03-19 13:04 ` rguenth at gcc dot gnu.org
2014-03-19 15:38 ` rguenth at gcc dot gnu.org
2014-03-19 16:42 ` marxin.liska at gmail dot com
2014-03-20 9:11 ` 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-60553-4-fc6hI92mLt@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).