public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/64043] New: [5 Regression] ICE (segfault) with LTO: in tree_check/tree.h:2758 get_binfo_at_offset/tree.c:11914
Date: Mon, 24 Nov 2014 09:59:00 -0000 [thread overview]
Message-ID: <bug-64043-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64043
Bug ID: 64043
Summary: [5 Regression] ICE (segfault) with LTO: in
tree_check/tree.h:2758
get_binfo_at_offset/tree.c:11914
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
Created attachment 34087
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34087&action=edit
Test case (unpack, run "make")
Using GCC 5.0.0 20141121, the attached program fails with the following ICE.
To reproduce: Unpack and hit "make". It will compile one.ii and two.ii and
gcc-ar them to libonetwo.ii; it compiles three.ii - and then LTOs them
together.
(Requires an LD with plugin capabilities; I've put the git version of binutils
into the path.)
The failure is:
0xa36e4f crash_signal
../../gcc/toplev.c:359
0xc97211 tree_check(tree_node*, char const*, int, char const*, tree_code)
../../gcc/tree.h:2758
0xc97211 get_binfo_at_offset(tree_node*, long, tree_node*)
../../gcc/tree.c:11914
0x884cf4 possible_polymorphic_call_targets(tree_node*, long,
ipa_polymorphic_call_context, bool*, void**, bool)
../../gcc/ipa-devirt.c:2404
0x7ef9d7 possible_polymorphic_call_targets(tree_node*, gimple_statement_base*,
bool*, void**)
../../gcc/ipa-utils.h:126
0x7edcd0 gimple_fold_call
../../gcc/gimple-fold.c:2667
0x7edcd0 fold_stmt_1
../../gcc/gimple-fold.c:3246
0xb55323 execute
../../gcc/tree-ssa-forwprop.c:2228
next reply other threads:[~2014-11-24 9:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 9:59 burnus at gcc dot gnu.org [this message]
2014-12-02 21:04 ` [Bug lto/64043] " hubicka at gcc dot gnu.org
2014-12-02 21:08 ` hubicka at gcc dot gnu.org
2014-12-02 21:20 ` jason at gcc dot gnu.org
2014-12-12 15:41 ` burnus at gcc dot gnu.org
2014-12-12 15:43 ` burnus at gcc dot gnu.org
2014-12-12 19:01 ` hubicka at gcc dot gnu.org
2014-12-15 3:42 ` hubicka at gcc dot gnu.org
2014-12-15 22:36 ` hubicka at gcc dot gnu.org
2014-12-16 11:22 ` schwab@linux-m68k.org
2014-12-17 14:29 ` dominiq at lps dot ens.fr
2014-12-22 15:03 ` izamyatin at gmail dot com
2014-12-22 15:17 ` hubicka at ucw dot cz
2014-12-22 15:36 ` izamyatin at gmail dot com
2015-01-12 7:47 ` izamyatin at gmail dot com
2015-01-14 6:37 ` hubicka at gcc dot gnu.org
2015-01-29 7:17 ` hubicka 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-64043-4@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).