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/65380] [5 Regression] LTO: ICE in add_symbol_to_partition_1, at lto/lto-partition.c:158
Date: Mon, 16 Mar 2015 07:52:00 -0000 [thread overview]
Message-ID: <bug-65380-4-41diFX5nph@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65380-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65380
--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #4)
> Hmm, this one compiles just fine for me with today mainline. Does the
> problem still reproduce for you? Can you possibly dump out node->debug()
> and c?
Unfortunately, it still fails for me with today's r221445 (for the very first
invocation of line lto-partition.c:158). For
157 gcc_assert (c != SYMBOL_EXTERNAL
158 && (c == SYMBOL_DUPLICATE || !symbol_partitioned_p (node)));
Running
lto1 -quiet -dumpbase one.o -mtune=generic -march=x86-64 -mtune=generic
-march=x86-64 -auxbase one -O2 -version -fexceptions -fmath-errno
-fsigned-zeros -ftrapping-math -fno-trapv -fno-openmp -fno-openacc
-fltrans-output-list=/tmp/ccX5yPa0.ltrans.out -fwpa -fresolution=two.res
@/tmp/ccYbGLe0
in the debugger gives:
(gdb) p c
$1 = SYMBOL_EXTERNAL
(gdb) p node->debug()
_ZTCSt14basic_ofstreamIcSt11char_traitsIcEE0_So/188
(_ZTCSt14basic_ofstreamIcSt11char_traitsIcEE0_So) @0x7ffff1d38880
Type: variable definition analyzed alias
Visibility: externally_visible external public visibility_specified
visibility:hidden virtual artificial
References: _ZTCN7Utility2IO12GUnzipStreamE0_So/7 (alias)
Referring: _ZTTSt14basic_ofstreamIcSt11char_traitsIcEE/178
(addr)_ZTTSt14basic_ofstreamIcSt11char_traitsIcEE/178 (addr)
Availability: available
Varpool flags: read-only const-value-known
$2 = void
next prev parent reply other threads:[~2015-03-16 7:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 16:43 [Bug lto/65380] New: " burnus at gcc dot gnu.org
2015-03-10 16:43 ` [Bug lto/65380] " burnus at gcc dot gnu.org
2015-03-10 19:55 ` hubicka at gcc dot gnu.org
2015-03-11 9:36 ` rguenth at gcc dot gnu.org
2015-03-11 10:29 ` burnus at gcc dot gnu.org
2015-03-16 0:36 ` hubicka at gcc dot gnu.org
2015-03-16 7:52 ` burnus at gcc dot gnu.org [this message]
2015-03-16 7:59 ` [Bug lto/65380] [5 Regression][ICF] " burnus at gcc dot gnu.org
2015-03-17 0:51 ` hubicka at ucw dot cz
2015-03-18 2:13 ` hubicka at gcc dot gnu.org
2015-03-18 2:14 ` hubicka at gcc dot gnu.org
2015-03-18 2:32 ` hubicka at gcc dot gnu.org
2015-03-18 8:22 ` burnus at gcc dot gnu.org
2015-03-18 13:19 ` marxin at gcc dot gnu.org
2015-03-18 18:28 ` hubicka at gcc dot gnu.org
2015-03-19 18:56 ` marxin 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-65380-4-41diFX5nph@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).