public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pfeifer@dbai.tuwien.ac.at (Gerald Pfeifer) To: gcc-gnats@gcc.gnu.org Subject: c++/10779: Date: Wed, 14 May 2003 12:26:00 -0000 [thread overview] Message-ID: <200305141217.h4ECH6pv069127@acrux.dbai.tuwien.ac.at> (raw) >Number: 10779 >Category: c++ >Synopsis: >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed May 14 12:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: >Release: 3.4 20030513 (experimental) >Organization: >Environment: System: FreeBSD acrux.dbai.tuwien.ac.at 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Mon May 5 14:20:44 CEST 2003 root@belatrix.dbai.tuwien.ac.at:/usr/src/sys/compile/DBAI i386 host: i386-unknown-freebsd4.8 build: i386-unknown-freebsd4.8 target: i386-unknown-freebsd4.8 configured with: /sw/test/gcc/cvs/configure --prefix=/sw/gcc-current --enable-languages=c,c++ >Description: The new C++ parser is not able to pinpoint the actual problem in the following piece of code, while GCC 3.3 has no problem doing so; GCC 3.3 issued a single error, while the new C++ parser prints a cascade of 10 error messages. static void InstantiateConstraint(const float&, unsigned, void(*AddFunction)(const TYPE&,bool&, char*, char*, unsigned*)); >How-To-Repeat: % g++3.3 x.cc x.cc:2: parse error before `&' token % gccvs x.cc x.cc:1: error: variable or field `InstantiateConstraint' declared void x.cc:1: error: expected primary-expression x.cc:1: error: expected primary-expression x.cc:2: error: `AddFunction' was not declared in this scope x.cc:2: error: expected primary-expression x.cc:2: error: expected primary-expression x.cc:3: error: expected primary-expression x.cc:3: error: expected primary-expression x.cc:4: error: expected primary-expression x.cc:4: error: initializer list being treated as compound expression >Fix: >Release-Note: >Audit-Trail: >Unformatted: >Subject: [3.4 regression] [new parser] Error cascade for unknown type in function prototype
reply other threads:[~2003-05-14 12:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200305141217.h4ECH6pv069127@acrux.dbai.tuwien.ac.at \ --to=pfeifer@dbai.tuwien.ac.at \ --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: 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).