public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9212: Internal compiler error in grokdeclarator, at cp/decl.c:11052 [gcc 3.2] Date: Tue, 07 Jan 2003 10:56:00 -0000 [thread overview] Message-ID: <20030107105604.29202.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9212; it has been noted by GNATS. From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, jjamison@cs.berkeley.edu Cc: Subject: Re: c++/9212: Internal compiler error in grokdeclarator, at cp/decl.c:11052 [gcc 3.2] Date: Tue, 7 Jan 2003 12:52:20 +0100 The ICE and the strange error messages when you remove some arguments of the constructor of LaoSyllable are fixed with the new parser in gcc 3.4. Here's a cleaned-up testcase: -----------------------------snip here---------------------------- struct A { enum E { e }; A(E); }; struct B { enum F { f }; B(F); }; struct C { C(A, B, A); }; C c(A(A::e), B(B::f), A(A::e)); -----------------------------snip here---------------------------- With gcc 3.4 20030106 I now get: bug.cc:18: error: cannot use `::' in parameter declaration bug.cc:18: error: cannot use `::' in parameter declaration bug.cc:18: error: cannot use `::' in parameter declaration I don't know whether these messages are correct - I also get them with other compilers, but I don't know why. Especially since "A a(A::e);" seems to be valid. I just leave that to the language experts. Regards, Volker http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9212
next reply other threads:[~2003-01-07 10:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-07 10:56 Volker Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-16 19:46 Nathan Sidwell 2003-01-16 19:36 Andreas Jaeger 2003-01-16 17:06 nathan 2003-01-07 11:20 nathan 2003-01-07 11:15 nathan 2003-01-07 6:06 jjamison
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=20030107105604.29202.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).