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 lto/54728] [4.8 regression] ICE in input_gimple_stmt, at gimple-streamer-in.c:254 Date: Fri, 21 Dec 2012 14:16:00 -0000 [thread overview] Message-ID: <bug-54728-4-QIefYX1jst@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54728-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54728 --- Comment #9 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-12-21 14:16:09 UTC --- When writting symtab_real_symbol_p I made external nodes to not be real symbols unless they are explicitelly called or refereed. The reason is that we keep around virtual extenral functions for possible devirtualization and I did not want those symbol appear to refereed in lto-plugin symbol table. While this works well with lto-plugin symbol table output it does not fare well with the use in lto-symtab. I am testing patch to separate both predicates.
next prev parent reply other threads:[~2012-12-21 14:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-27 11:46 [Bug lto/54728] New: " dimhen at gmail dot com 2012-09-27 12:17 ` [Bug lto/54728] " rguenth at gcc dot gnu.org 2012-09-27 12:28 ` dimhen at gmail dot com 2012-10-01 10:17 ` dimhen at gmail dot com 2012-10-11 7:07 ` d.g.gorbachev at gmail dot com 2012-10-11 7:08 ` d.g.gorbachev at gmail dot com 2012-10-11 7:08 ` d.g.gorbachev at gmail dot com 2012-11-16 3:36 ` pinskia at gcc dot gnu.org 2012-12-07 11:25 ` rguenth at gcc dot gnu.org 2012-12-21 14:16 ` hubicka at gcc dot gnu.org [this message] 2012-12-21 15:01 ` hubicka at gcc dot gnu.org 2012-12-22 23:28 ` hubicka at gcc dot gnu.org 2013-01-02 10:41 ` rguenth at gcc dot gnu.org 2013-01-02 13:48 ` dimhen at gmail dot com
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-54728-4-QIefYX1jst@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).