public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8143: g++ gives an ice Date: Thu, 10 Oct 2002 14:36:00 -0000 [thread overview] Message-ID: <20021010213601.7436.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8143; it has been noted by GNATS. From: Reichelt <reichelt@igpm.rwth-aachen.de> To: ruggero@wam.umd.edu, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/8143: g++ gives an ice Date: Fri, 11 Oct 2002 00:24:14 +0200 Hi, the parser chokes on the following illegal code snippet (X is undefined): ---------------------------snip here--------------------------- struct foo { X x; foo(X) {} foo(X y, int) : x() {} }; ---------------------------snip here--------------------------- The error messages with gcc 3.1 are: bug.cc:3: 'X' is used as a type, but is not defined as a type. bug.cc:5: parse error before `)' token bug.cc:5: missing ';' before right brace bug.cc:6: `X' was not declared in this scope bug.cc:6: parse error before `,' token bug.cc:6: ISO C++ forbids defining types within return type bug.cc:6: semicolon missing after declaration of `struct foo' bug.cc: In function `int foo(...)': bug.cc:6: only constructors take base initializers bug.cc:6: confused by earlier errors, bailing out Gcc 2.95.x and 3.0.x handle the situation gracefully. Gcc 3.1 and 3.2 produce "confused by earlier errors, bailing out" and the main trunk ICEs (checked on i686-pc-linux-gnu and mips-sgi-irix6.5). Greetings, Volker Reichelt http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8143
next reply other threads:[~2002-10-10 21:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-10 14:36 Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-30 15:21 reichelt 2002-10-04 8:08 lerdsuwa 2002-10-04 7:26 ruggero
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=20021010213601.7436.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).