public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/58733] [4.9 Regression] ICE in operator[], at vec.h:827
Date: Sat, 18 Jan 2014 20:40:00 -0000 [thread overview]
Message-ID: <bug-58733-4-FsxSGUhDyO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58733-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58733
--- Comment #10 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
With gold I get:
markus@x4 lto % cat 20090302_0.C
/* { dg-lto-do link } */
/* { dg-require-effective-target fpic } */
/* { dg-lto-options {{-fPIC -flto -flto-partition=1to1 -r -nostdlib}} } */
struct Foo {
bool Mumble();
static void Bar() { if (foo_->Mumble()) foo_ = 0; }
static void Baz() { Bar(); }
static Foo *foo_;
};
void Unused() { Foo::Bar(); Foo::Baz(); }
markus@x4 lto % g++ -fPIC -flto -r -nostdlib 20090302_0.C
lto1: internal compiler error: in operator[], at vec.h:719
0x54b227 vec<inline_summary, va_gc, vl_embed>::operator[](unsigned int)
../../gcc/gcc/vec.h:719
0x54cd04 vec<inline_summary, va_gc, vl_embed>::operator[](unsigned int)
../../gcc/gcc/vec.h:1167
0x54cd04 inline_summary
../../gcc/gcc/ipa-inline.h:244
0x54cd04 lto_balanced_map()
../../gcc/gcc/lto/lto-partition.c:502
0x547d76 do_whole_program_analysis
../../gcc/gcc/lto/lto.c:3161
0x547d76 lto_main()
../../gcc/gcc/lto/lto.c:3301
markus@x4 lto % cat 20090302_0.res
1
20090302_0.o 5
181 afeebb30522d796 PREVAILING_DEF _ZN3Foo3BarEv
184 afeebb30522d796 PREVAILING_DEF _ZN3Foo3BazEv
187 afeebb30522d796 PREVAILING_DEF _Z6Unusedv
203 afeebb30522d796 UNDEF _ZN3Foo4foo_E
200 afeebb30522d796 UNDEF _ZN3Foo6MumbleEv
_ZN3Foo3BazEv/1 (Baz) @0x7f5f7ba71000
Type: function definition analyzed
Visibility: externally_visible prevailing_def public weak comdat
comdat_group:_ZN3Foo3BazEv one_only
References:
Referring: _ZN3Foo3BazEv.localalias.0/7 (alias)
With bfd the symbols are PREVAILING_DEF_IRONLY_EXP:
markus@x4 foo % cat 20090302_0.res
1
20090302_0.o 5
181 8c3642f7b0939cf4 PREVAILING_DEF_IRONLY_EXP _ZN3Foo3BarEv
184 8c3642f7b0939cf4 PREVAILING_DEF_IRONLY_EXP _ZN3Foo3BazEv
187 8c3642f7b0939cf4 PREVAILING_DEF_IRONLY_EXP _Z6Unusedv
203 8c3642f7b0939cf4 UNDEF _ZN3Foo4foo_E
200 8c3642f7b0939cf4 UNDEF _ZN3Foo6MumbleEv
markus@x4 foo %
_ZN3Foo3BazEv/1 (Baz) @0x7f5166ec1000
Type: function definition analyzed
Visibility: prevailing_def_ironly
References:
Referring:
next prev parent reply other threads:[~2014-01-18 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 6:55 [Bug lto/58733] New: " markus at trippelsdorf dot de
2013-10-15 8:01 ` [Bug lto/58733] " rguenth at gcc dot gnu.org
2013-11-05 15:04 ` rguenth at gcc dot gnu.org
2013-11-05 15:22 ` octoploid at yandex dot com
2013-11-06 13:15 ` octoploid at yandex dot com
2013-11-22 11:03 ` rguenth at gcc dot gnu.org
2013-11-22 11:37 ` octoploid at yandex dot com
2013-11-22 13:53 ` hjl.tools at gmail dot com
2013-12-04 15:05 ` jakub at gcc dot gnu.org
2013-12-04 15:41 ` octoploid at yandex dot com
2014-01-16 11:05 ` trippels at gcc dot gnu.org
2014-01-18 20:40 ` trippels at gcc dot gnu.org [this message]
2014-03-02 22:31 ` hubicka at gcc dot gnu.org
2014-03-02 22:33 ` hubicka at gcc dot gnu.org
2014-03-03 7:56 ` trippels 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-58733-4-FsxSGUhDyO@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).