public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/47274] [4.6 regression] ICE in lto_varpool_replace_node, at lto-symtab.c:306
Date: Mon, 17 Jan 2011 16:11:00 -0000 [thread overview]
Message-ID: <bug-47274-4-GT8qmIxeaC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47274-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47274
--- Comment #8 from Jan Hubicka <hubicka at ucw dot cz> 2011-01-17 16:03:37 UTC ---
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47274
>
> --- Comment #7 from John David Anglin <danglin at gcc dot gnu.org> 2011-01-17 15:42:26 UTC ---
> Resolution file is:
>
> 3
> abs-1.o 3
> 70 262910e5 PREEMPTED_IR main_test
> 84 262910e5 PREEMPTED_IR abs
> 88 262910e5 PREEMPTED_IR abs_called
> abs-1-lib.o 3
> 70 b13b015b PREVAILING_DEF_IRONLY abs
> 101 b13b015b PREEMPTED_IR inside_main
> 103 b13b015b PREVAILING_DEF_IRONLY abs_called
> main.o 3
> 70 e5772d37 PREVAILING_DEF main
> 76 e5772d37 PREVAILING_DEF_IRONLY main_test
> 79 e5772d37 PREVAILING_DEF_IRONLY inside_main
>
> /tmp/ccJGcG05.lto.o is empty:
> dave@gsyprf11:~/gcc-4.6/objdir/gcc/testsuite/gcc$ ls -l /tmp/ccJGcG05.lto.o
> -rw------- 1 dave users 0 Jan 17 07:20 /tmp/ccJGcG05.lto.o
>
> Assert fails at this point:
>
> Breakpoint 1, lto_varpool_replace_node (prevailing_node=0x404591c0,
> vnode=0x40459150) at ../../gcc/gcc/lto-symtab.c:306
> 306 gcc_assert (!vnode->analyzed || prevailing_node->analyzed);
> (gdb) p vnode->analyzed
> $7 = 1
> (gdb) p prevailing_node->analyzed
> $8 = 0
We need to debug how the defined node ends up to be unanalyzed.
I assume it is abs_called variable?
It seems that we get wrong already when streaming abs-1-lib.o file. Would be
possible to attach cgraph dump from WPA?
Honza
next prev parent reply other threads:[~2011-01-17 16:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 23:54 [Bug lto/47274] New: " schwab@linux-m68k.org
2011-01-13 11:01 ` [Bug lto/47274] " rguenth at gcc dot gnu.org
2011-01-13 16:59 ` schwab@linux-m68k.org
2011-01-15 2:28 ` anton at samba dot org
2011-01-15 6:39 ` howarth at nitro dot med.uc.edu
2011-01-15 22:55 ` schwab@linux-m68k.org
2011-01-17 14:09 ` rguenth at gcc dot gnu.org
2011-01-17 15:53 ` danglin at gcc dot gnu.org
2011-01-17 16:11 ` hubicka at ucw dot cz [this message]
2011-01-17 16:14 ` hubicka at ucw dot cz
2011-01-17 17:00 ` rguenth at gcc dot gnu.org
2011-01-17 17:02 ` rguenth at gcc dot gnu.org
2011-01-17 19:07 ` dave at hiauly1 dot hia.nrc.ca
2011-01-17 19:16 ` dave at hiauly1 dot hia.nrc.ca
2011-01-18 1:37 ` dave at hiauly1 dot hia.nrc.ca
2011-01-18 1:37 ` dave at hiauly1 dot hia.nrc.ca
2011-01-20 2:25 ` dave at hiauly1 dot hia.nrc.ca
2011-01-20 14:31 ` jakub at gcc dot gnu.org
2011-01-27 16:02 ` hubicka at gcc dot gnu.org
2011-01-27 17:21 ` dave at hiauly1 dot hia.nrc.ca
2011-01-27 17:27 ` Jan Hubicka
2011-01-27 17:28 ` hubicka at ucw dot cz
2011-01-27 19:44 ` dave at hiauly1 dot hia.nrc.ca
2011-01-31 17:43 ` hubicka at gcc dot gnu.org
2011-01-31 17:57 ` davek at gcc dot gnu.org
2011-01-31 19:41 ` davek at gcc dot gnu.org
2011-01-31 20:22 ` dave at hiauly1 dot hia.nrc.ca
2011-01-31 20:28 ` davek at gcc dot gnu.org
2011-02-01 0:27 ` dave at hiauly1 dot hia.nrc.ca
2011-02-01 0:37 ` dave at hiauly1 dot hia.nrc.ca
2011-02-01 7:00 ` davek at gcc dot gnu.org
2011-02-01 19:43 ` hubicka at ucw dot cz
2011-02-01 21:05 ` davek at gcc dot gnu.org
2011-02-02 16:08 ` jakub at gcc dot gnu.org
2011-02-02 16:42 ` schwab@linux-m68k.org
2011-02-02 16:48 ` schwab@linux-m68k.org
2011-02-02 16:57 ` jakub at gcc dot gnu.org
2011-02-03 10:49 ` jakub at gcc dot gnu.org
2011-02-03 10:59 ` jakub 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-47274-4-GT8qmIxeaC@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).