public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/65858] ICE in varpool_node::get_constructor during chromium build on arm-linux-gnueabihf with LTO during LINK chrome Date: Thu, 23 Apr 2015 16:37:00 -0000 [thread overview] Message-ID: <bug-65858-4-5Oa8DP8kSm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65858 --- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Those two bugs seems to be caused by same issue. Unforutnately it is bit hard to guess what it is coming from - it seems that we manage to store error_mark_node into the LTO object file. If you can patch your GCC tree, the following (untested) patch should bring the ICE from link time to compile time making it easier to reproduce (I build chromium on x86_64 and did not see this crash) Index: lto-streamer-out.c =================================================================== --- lto-streamer-out.c (revision 222160) +++ lto-streamer-out.c (working copy) @@ -2149,6 +2149,7 @@ /* Output DECL_INITIAL for the function, which contains the tree of lexical scopes. */ stream_write_tree (ob, DECL_INITIAL (var), true); + gcc_assert (DECL_INITIAL (var) != error_mark_node); /* Create a section to hold the pickled output of this function. */ produce_asm (ob, var);
next parent reply other threads:[~2015-04-23 16:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65858-4@http.gcc.gnu.org/bugzilla/> 2015-04-23 16:37 ` hubicka at gcc dot gnu.org [this message] 2015-04-27 15:47 ` prathamesh3492 at gcc dot gnu.org 2015-04-30 16:22 ` prathamesh3492 at gcc dot gnu.org 2015-04-30 19:48 ` [Bug c++/65858] [5/6 Regression] " paolo.carlini at oracle dot com 2015-05-01 18:44 ` paolo at gcc dot gnu.org 2015-05-01 18:48 ` paolo at gcc dot gnu.org 2015-05-01 18:55 ` paolo.carlini at oracle dot com 2015-05-01 22:00 ` prathamesh3492 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-65858-4-5Oa8DP8kSm@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).