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++/19964] New: [3.4/4.0 regression] ICE on invalid member declaration
Date: Tue, 15 Feb 2005 09:30:00 -0000 [thread overview]
Message-ID: <20050215004355.19964.reichelt@gcc.gnu.org> (raw)
The following invalid code snippet causes an ICE since gcc 3.4.0:
==================
struct A
{
A : A;
};
==================
bug.cc:3: error: expected primary-expression before ';' token
bug.cc:3: error: name 'A' has incomplete type
bug.cc:2: internal compiler error: Segmentation fault
Please submit a full bug report, [etc.]
With the similar code snippet
==================
struct A
{
A : B;
};
==================
I get an ICE since at least gcc 2.95.3.
bug.cc:3: error: 'B' was not declared in this scope
bug.cc:3: error: name 'A' has incomplete type
bug.cc:2: internal compiler error: Segmentation fault
Please submit a full bug report, [etc.]
--
Summary: [3.4/4.0 regression] ICE on invalid member declaration
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=19964
next reply other threads:[~2005-02-15 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 9:30 reichelt at gcc dot gnu dot org [this message]
2005-02-15 11:42 ` [Bug c++/19964] " pinskia at gcc dot gnu dot org
2005-02-15 12:18 ` reichelt at gcc dot gnu dot org
2005-05-19 17:35 ` [Bug c++/19964] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-07-22 21:18 ` pinskia at gcc dot gnu dot org
2005-09-15 11:51 ` nathan at gcc dot gnu dot org
2005-09-27 16:14 ` 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=20050215004355.19964.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).