public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: snyder@fnal.gov To: gcc-gnats@gcc.gnu.org Subject: c++/7566: g++ 3.3 ICE: Error reporting routines re-entered. Date: Sat, 10 Aug 2002 10:16:00 -0000 [thread overview] Message-ID: <200208101712.MAA03178@d0sgibnl1.fnal.gov> (raw) >Number: 7566 >Category: c++ >Synopsis: g++ 3.3 ICE: Error reporting routines re-entered. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Sat Aug 10 10:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: scott snyder >Release: 3.3 20020808 (experimental) >Organization: <organization of PR author (multiple lines)> >Environment: System: Linux karma 2.4.9-13 #1 Tue Oct 30 20:11:04 EST 2001 i686 unknown 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: ../egcs/configure --prefix=/usr/local/egcs --enable-threads=posix --enable-long-long : (reconfigured) : (reconfigured) >Description: gcc crashes on the following (invalid) input: $ g++ -c y.cc y.cc: In function `void foo(int)': y.cc:11: error: jump to case label y.cc:8: error: crosses initialization of `bar x' Internal compiler error: Error reporting routines re-entered. Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. $ >How-To-Repeat: --------------------------------------------------- struct bar { bar(); ~bar();}; void foo (int c) { switch (c) { case 0: case 1: bar x; break; default: break; } } --------------------------------------------------- >Fix: <how to correct or work around the problem, if known (multiple lines)> >Release-Note: >Audit-Trail: >Unformatted: SEND-PR: Leave "Confidential" as "no"; all GCC PRs are public. SEND-PR: critical GCC is completely not operational; no work-around known. SEND-PR: serious GCC is not working properly; a work-around is possible. SEND-PR: non-critical Report indicates minor problem. SEND-PR: medium The problem should be solved in the next release. SEND-PR: low The problem should be solve in a future release. SEND-PR: doc-bug The documentation is incorrect. SEND-PR: accepts-illegal GCC fails to reject erroneous code. SEND-PR: rejects-legal GCC gives an error message for correct code. SEND-PR: wrong-code The machine code generated by gcc is incorrect. SEND-PR: ice-on-legal-code GCC gives an Internal Compiler Error (ICE) SEND-PR: for correct code SEND-PR: ice-on-illegal-code GCC gives an ICE instead of reporting an error SEND-PR: pessimizes-code GCC misses an important optimization opportunity SEND-PR: sw-bug Software bug of some other class than above SEND-PR: change-request A feature in GCC is missing. SEND-PR: support I need help with gcc.
next reply other threads:[~2002-08-10 17:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-10 10:16 snyder [this message] 2002-08-14 13:16 gdr
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=200208101712.MAA03178@d0sgibnl1.fnal.gov \ --to=snyder@fnal.gov \ --cc=gcc-gnats@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).