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++/28258] New: [4.0/4.1/4.2 regression] ICE with invalid constructor
Date: Tue, 04 Jul 2006 23:52:00 -0000 [thread overview]
Message-ID: <bug-28258-1771@http.gcc.gnu.org/bugzilla/> (raw)
The following invalid testcase triggers an ICE since GCC 3.0:
=========================================
struct A
{
A(void x);
};
struct B : A {};
B b;
=========================================
bug.cc:3: error: 'x' has incomplete type
bug.cc:3: error: invalid use of 'void'
bug.cc:8: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in locate_copy, at cp/method.c:946
Please submit a full bug report, [tc.]
--
Summary: [4.0/4.1/4.2 regression] ICE with invalid constructor
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Keywords: ice-on-invalid-code, error-recovery, monitored
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: reichelt at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28258
next reply other threads:[~2006-07-04 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 23:52 reichelt at gcc dot gnu dot org [this message]
2006-07-04 23:56 ` [Bug c++/28258] " pinskia at gcc dot gnu dot org
2006-07-17 3:06 ` mmitchel at gcc dot gnu dot org
2006-07-17 22:06 ` lmillward at gcc dot gnu dot org
2006-07-18 17:22 ` lmillward at gcc dot gnu dot org
2006-07-18 17:23 ` [Bug c++/28258] [4.0/4.1 " lmillward at gcc dot gnu dot org
2006-07-22 14:03 ` lmillward at gcc dot gnu dot org
2006-07-22 14:08 ` lmillward at gcc dot gnu dot org
2006-07-22 14:08 ` lmillward 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=bug-28258-1771@http.gcc.gnu.org/bugzilla/ \
--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).