From: Steve Ellcey <sje@cup.hp.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org, dave.anglin@nrc-cnrc.gc.ca
Subject: Re: PR c/43288 (ICE with __attribute__ ((common)))
Date: Wed, 17 Mar 2010 15:56:00 -0000 [thread overview]
Message-ID: <1268841214.9544.48.camel@hpsje.cup.hp.com> (raw)
In-Reply-To: <20100317153505.GB14802@atrey.karlin.mff.cuni.cz>
On Wed, 2010-03-17 at 16:35 +0100, Jan Hubicka wrote:
> Hmm, I rebuilt for this tripplet, but still no luck:
>
> jh@gcc14:~/trunk/build-hppa2/gcc$ cat a.C
> class t { virtual ~t(); };
> namespace __cxxabiv1 {
> class __fundamental_type_info : public t {};
> }
>
> jh@gcc14:~/trunk/build-hppa2/gcc$ ./cc1plus a.C -quiet
> jh@gcc14:~/trunk/build-hppa2/gcc$
>
> There seems to be no changes today that would fix this. If the testcase seems
> fine, could you try to get a backtrace for me? I think we might only need to
> avoid make_decl_rtl from being called too early.
>
> Honza
The test looks fine. It still fails for me on ToT. I don't think the
backtrace to the abort helps much, it is coming from
cp_write_global_declarations() which is iterating over
unemitted_tinfo_decls and I think we need to understand more about when
and how the decls are put on this list.
Steve Ellcey
sje@cup.hp.com
#0 fancy_abort ()
at /proj/opensrc/sje/reg/src/trunk/gcc/diagnostic.c:763
#1 0x878858 in make_decl_rtl ()
at /proj/opensrc/sje/reg/src/trunk/gcc/varasm.c:1445
#2 0x879540 in notice_global_symbol ()
at /proj/opensrc/sje/reg/src/trunk/gcc/varasm.c:1621
#3 0x8f2120 in varpool_enqueue_needed_node ()
at /proj/opensrc/sje/reg/src/trunk/gcc/varpool.c:202
#4 0x8f2748 in varpool_finalize_decl ()
at /proj/opensrc/sje/reg/src/trunk/gcc/varpool.c:307
#5 0x709790 in rest_of_decl_compilation ()
at /proj/opensrc/sje/reg/src/trunk/gcc/passes.c:195
#6 0x921b0 in make_rtl_for_nonlocal_decl ()
at /proj/opensrc/sje/reg/src/trunk/gcc/cp/decl.c:5367
#7 0x96450 in cp_finish_decl ()
at /proj/opensrc/sje/reg/src/trunk/gcc/cp/decl.c:5904
#8 0x23cf90 in emit_tinfo_decl ()
at /proj/opensrc/sje/reg/src/trunk/gcc/cp/rtti.c:1555
#9 0x1d8a54 in cp_write_global_declarations ()
at /proj/opensrc/sje/reg/src/trunk/gcc/cp/decl2.c:3581
#10 0x766640 in compile_file ()
at /proj/opensrc/sje/reg/src/trunk/gcc/toplev.c:1065
#11 0x769e44 in do_compile ()
at /proj/opensrc/sje/reg/src/trunk/gcc/toplev.c:2409
#12 0x769fc4 in toplev_main ()
at /proj/opensrc/sje/reg/src/trunk/gcc/toplev.c:2451
#13 0x3f9c5c in main () at /proj/opensrc/sje/reg/src/trunk/gcc/main.c:35
next prev parent reply other threads:[~2010-03-17 15:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 15:33 Jan Hubicka
2010-03-10 15:49 ` Richard Guenther
2010-03-11 21:27 ` Steve Ellcey
2010-03-11 22:03 ` John David Anglin
2010-03-12 0:19 ` Steve Ellcey
2010-03-17 15:35 ` Jan Hubicka
2010-03-17 15:43 ` Steve Ellcey
2010-03-17 15:53 ` Jan Hubicka
2010-03-17 15:56 ` Steve Ellcey [this message]
2010-03-17 17:00 ` Jan Hubicka
2010-03-18 0:48 ` Jan Hubicka
2010-03-19 4:47 ` Steve Ellcey
2010-03-19 13:51 ` John David Anglin
2010-03-27 13:15 ` Richard Guenther
2010-03-27 13:45 ` Jan Hubicka
[not found] <303e1d291003120626v7f427074uacee4953a2efc21e@mail.gmail.com>
[not found] ` <alpine.LNX.2.00.1003121537120.5522@zhemvz.fhfr.qr>
2010-03-12 16:59 ` David Edelsohn
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=1268841214.9544.48.camel@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
/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).