public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/18177] New: [4.0 regression] ICE with const_cast for undeclared variable Date: Wed, 27 Oct 2004 13:54:00 -0000 [thread overview] Message-ID: <20041027135414.18177.reichelt@gcc.gnu.org> (raw) The following invalid code snippet causes an ICE when compiled with mainline: ============================= void foo() { X; const_cast<int&>(X); } ============================= bug.cc: In function `void foo()': bug.cc:3: error: 'X' was not declared in this scope bug.cc:4: internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in build_pointer_type_for_mode, at tree.c:4118 Please submit a full bug report, [etc.] The regression appeared in March 2004: : Search converges between 2004-03-01-trunk (#446) and 2004-04-01-trunk (#447). -- Summary: [4.0 regression] ICE with const_cast for undeclared variable Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, error-recovery, monitored Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18177
next reply other threads:[~2004-10-27 13:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-27 13:54 reichelt at gcc dot gnu dot org [this message] 2004-10-27 13:58 ` [Bug c++/18177] " pinskia at gcc dot gnu dot org 2004-10-27 14:29 ` reichelt at gcc dot gnu dot org 2004-10-28 18:19 ` mmitchel at gcc dot gnu dot org 2004-11-03 2:48 ` cvs-commit at gcc dot gnu dot org 2004-11-03 2:56 ` mmitchel 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=20041027135414.18177.reichelt@gcc.gnu.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: 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).