public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/19367] New: 4.0: ICE: tree_check in lookup_local_die with local `using' Date: Mon, 10 Jan 2005 21:39:00 -0000 [thread overview] Message-ID: <20050110213919.19367.snyder@fnal.gov> (raw) g++ dies with a tree check ICE when the source below is compiled with -g: $ cc1plus -g x.cc void foo() x.cc:6: internal compiler error: tree check: expected class 'declaration', have 'exceptional' (@@dummy) in lookup_decl_die, at dwarf2out.c:5415 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. $ Environment: System: Linux karma 2.6.8.1 #20 Mon Sep 13 23:48:47 EDT 2004 i686 i686 i386 GNU/Linux Architecture: i686 <machine, os, target, libraries (multiple lines)> host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: /home/sss/gcc/gcc/configure --prefix=/usr/local/gcc --enable-threads=posix --enable-long-long --enable-languages=c,c++,f95 How-To-Repeat: Compile with -g: ---------------------------------------- int toupper (int); namespace std { using ::toupper; } void foo() { using std::toupper; } ---------------------------------------- ------- Additional Comments From snyder at fnal dot gov 2005-01-10 21:39 ------- Fix: <how to correct or work around the problem, if known (multiple lines)> -- Summary: 4.0: ICE: tree_check in lookup_local_die with local `using' Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: snyder at fnal dot gov CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19367
next reply other threads:[~2005-01-10 21:39 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-10 21:39 gcc-bugzilla at gcc dot gnu dot org [this message] 2005-01-10 21:56 ` [Bug debug/19367] [4.0 Regression] " pinskia at gcc dot gnu dot org 2005-01-10 22:55 ` Daniel Berlin 2005-01-10 22:55 ` dberlin at dberlin dot org 2005-01-11 0:53 ` pinskia at gcc dot gnu dot org 2005-01-11 1:32 ` giovannibajo at libero dot it 2005-01-11 1:36 ` [Bug c++/19367] " pinskia at gcc dot gnu dot org 2005-01-11 1:42 ` pinskia at gcc dot gnu dot org 2005-01-19 18:41 ` pinskia at gcc dot gnu dot org 2005-01-25 16:11 ` pinskia at gcc dot gnu dot org 2005-01-31 2:11 ` mmitchel at gcc dot gnu dot org 2005-01-31 4:08 ` cvs-commit at gcc dot gnu dot org 2005-01-31 4:13 ` mmitchel at gcc dot gnu dot org 2005-02-28 15:16 ` cvs-commit 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=20050110213919.19367.snyder@fnal.gov \ --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: linkBe 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).