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++/20147] New: [3.4/4.0 regression] ICE on undefined variable in statement expression
Date: Tue, 22 Feb 2005 22:02:00 -0000 [thread overview]
Message-ID: <20050222165807.20147.reichelt@gcc.gnu.org> (raw)
The C++ frontend issues an ICE when compiling the following invalid
code snippet:
================
void foo()
{
({x;});
}
================
bug.cc: In function 'void foo()':
bug.cc:3: error: 'x' was not declared in this scope
bug.cc:3: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in finish_stmt_expr_expr, at cp/semantics.c:1546
Please submit a full bug report, [etc.]
The appeared in gcc 3.4.0.
--
Summary: [3.4/4.0 regression] ICE on undefined variable in
statement expression
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=20147
next reply other threads:[~2005-02-22 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 22:02 reichelt at gcc dot gnu dot org [this message]
2005-02-22 22:06 ` [Bug c++/20147] " pinskia at gcc dot gnu dot org
2005-02-23 10:35 ` pinskia at gcc dot gnu dot org
2005-03-17 18:32 ` [Bug c++/20147] [3.4/4.0/4.1 " pcarlini at suse dot de
2005-03-17 22:11 ` pinskia at gcc dot gnu dot org
2005-03-21 11:50 ` cvs-commit at gcc dot gnu dot org
2005-03-21 11:53 ` cvs-commit at gcc dot gnu dot org
2005-03-21 12:50 ` [Bug c++/20147] [3.4/4.0 " cvs-commit at gcc dot gnu dot org
2005-03-21 12:55 ` cvs-commit at gcc dot gnu dot org
2005-03-21 15:26 ` cvs-commit at gcc dot gnu dot org
2005-03-21 15:37 ` cvs-commit at gcc dot gnu dot org
2005-03-21 15:37 ` pcarlini at suse dot de
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=20050222165807.20147.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: 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).