public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gccbugs at contacts dot eelis dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11862] New: ICE on illegal code, in cp_parser_template_id, at cp/parser.c:7515 Date: Sat, 09 Aug 2003 03:59:00 -0000 [thread overview] Message-ID: <20030809035908.11862.gccbugs@contacts.eelis.net> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11862 Summary: ICE on illegal code, in cp_parser_template_id, at cp/parser.c:7515 Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gccbugs at contacts dot eelis dot net CC: gcc-bugs at gcc dot gnu dot org The following single (illegal) line: template <typename> void x (y); x< causes an ICE in GCC version 3.4 20030723: t.cpp:1: error: variable or field `x' declared void t.cpp:1: error: template declaration of `int x' t.cpp:1: error: `y' was not declared in this scope t.cpp:2: internal compiler error: in cp_parser_template_id, at cp/parser.c:7515 GCC version 3.2.3 reports the following errors: t.cpp:1: variable or field `x' declared void t.cpp:1: template declaration of `int x' t.cpp:2: parse error at end of input and doesn't end with an ICE (btw: those first two aren't very good errors). (Is this phenomenon of bugs being introduced in newer versions known as 'regression'?)
next reply other threads:[~2003-08-09 3:59 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-09 3:59 gccbugs at contacts dot eelis dot net [this message] 2003-08-09 4:09 ` [Bug c++/11862] [3.4 Regression] " pinskia at gcc dot gnu dot org 2003-08-11 14:54 ` bangerth at dealii dot org 2003-10-19 13:48 ` lerdsuwa 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=20030809035908.11862.gccbugs@contacts.eelis.net \ --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: 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).