public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/31899] [4.2/4.3 regression] -g and using declaration causing ICE in reference_to_unused
Date: Tue, 02 Oct 2007 16:55:00 -0000 [thread overview]
Message-ID: <20071002165546.2325.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31899-1827@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from rguenth at gcc dot gnu dot org 2007-10-02 16:55 -------
else if (!cgraph_global_info_ready
&& (TREE_CODE (*tp) == VAR_DECL || TREE_CODE (*tp) ==
FUNCTION_DECL))
gcc_unreachable ();
the problem is that the C++ FE emits debug info for global using decls from
parsing:
...
#9 0x082a825e in cp_emit_debug_info_for_using (t=0xb7d6705c, context=0x0)
at /home/richard/src/trunk/gcc/cp/name-lookup.c:5223
---Type <return> to continue, or q <return> to quit---
#10 0x0829f5ef in do_toplevel_using_decl (decl=0xb7d61870, scope=0xb7d61798,
name=0xb7d66708) at /home/richard/src/trunk/gcc/cp/name-lookup.c:3360
#11 0x081bca90 in cp_parser_using_declaration (parser=0xb7cd22a4,
access_declaration_p=0 '\0')
at /home/richard/src/trunk/gcc/cp/parser.c:11695
...
via the imported_module_or_decl debug hook. I guess we should simply queue
these with the varpool. Or probably invent a new pool for just this use.
Or just weaken the sanity check.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31899
next prev parent reply other threads:[~2007-10-02 16:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 13:09 [Bug c++/31899] New: " zak at transversal dot com
2007-05-11 17:53 ` [Bug c++/31899] " fang at csl dot cornell dot edu
2007-05-11 17:58 ` fang at csl dot cornell dot edu
2007-05-12 13:50 ` [Bug debug/31899] " pinskia at gcc dot gnu dot org
2007-05-14 21:29 ` mmitchel at gcc dot gnu dot org
2007-07-04 3:06 ` mmitchel at gcc dot gnu dot org
2007-07-20 3:52 ` mmitchel at gcc dot gnu dot org
2007-07-27 20:54 ` dougkwan at google dot com
2007-08-08 18:59 ` pinskia at gcc dot gnu dot org
2007-10-02 16:22 ` pinskia at gcc dot gnu dot org
2007-10-02 16:22 ` pinskia at gcc dot gnu dot org
2007-10-02 16:55 ` rguenth at gcc dot gnu dot org [this message]
2007-10-02 17:06 ` rguenth at gcc dot gnu dot org
2007-10-02 17:12 ` rguenth at gcc dot gnu dot org
2007-10-03 10:02 ` rguenth at gcc dot gnu dot org
2007-10-03 10:04 ` [Bug debug/31899] [4.2 Regression] " rguenth at gcc dot gnu dot org
2007-10-05 12:14 ` rguenth at gcc dot gnu dot org
2007-10-10 9:29 ` rguenth at gcc dot gnu dot org
2007-10-10 9:29 ` rguenth at gcc dot gnu dot org
2008-02-27 13:24 ` rguenth at gcc dot gnu dot 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=20071002165546.2325.qmail@sourceware.org \
--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).