public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: snyder@fnal.gov
To: gcc-gnats@gcc.gnu.org
Subject: c++/5548: g++ 3.1 ICE on invalid input
Date: Wed, 30 Jan 2002 16:36:00 -0000 [thread overview]
Message-ID: <200201310029.g0V0T1x16112@karma.fnal.gov> (raw)
>Number: 5548
>Category: c++
>Synopsis: g++ 3.1 ICE on invalid input
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-illegal-code
>Submitter-Id: net
>Arrival-Date: Wed Jan 30 16:36:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: scott snyder
>Release: 3.1 20020129 (experimental)
>Organization:
>Environment:
System: Linux karma 2.4.9-13 #1 Tue Oct 30 20:11:04 EST 2001 i686 unknown
Architecture: i686
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
>Description:
g++ dies with a segv compiling the source below (which is invalid C++):
$ g++ -c x.cc
x.cc:3: parse error before `x'
x.cc:3: missing ';' before right brace
x.cc:4: ISO C++ forbids defining types within return type
x.cc:4: semicolon missing after declaration of `struct Item'
x.cc: In function `int Item()':
x.cc:4: only constructors take base initializers
x.cc:4: internal error: Segmentation fault
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:
Compile this source:
-------------------------------------------------------------------
struct Item {
int what;
Item(string x) {}
Item() : what(0) {}
};
-------------------------------------------------------------------
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-01-31 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 16:36 snyder [this message]
2002-05-28 7:21 lerdsuwa
2003-01-01 13:35 neroden
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=200201310029.g0V0T1x16112@karma.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: 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).