public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org, rogier.goossens@cmg.nl Subject: Re: c/3379: gcc 3.0 gives incomprehensible error using explicit __func__ Date: Fri, 20 Jul 2001 14:50:00 -0000 [thread overview] Message-ID: <20010720215029.26192.qmail@sourceware.cygnus.com> (raw) Synopsis: gcc 3.0 gives incomprehensible error using explicit __func__ State-Changed-From-To: open->analyzed State-Changed-By: jsm28 State-Changed-When: Fri Jul 20 14:50:29 2001 State-Changed-Why: Confirmed as a bug. This is a regression in 3.0 relative to 2.95.3; both 2.95.3 and 3.1 CVS give 'parse error before "__func__"' so if this regression isn't felt worth fixing on the 3.0 branch then the PR can be closed as fixed in 3.1. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3379&database=gcc
next reply other threads:[~2001-07-20 14:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-20 14:50 jsm28 [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-03 14:21 mmitchel 2002-03-29 12:26 mmitchel 2001-06-22 11:56 rogier.goossens
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=20010720215029.26192.qmail@sourceware.cygnus.com \ --to=jsm28@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=jsm28@cam.ac.uk \ --cc=nobody@gcc.gnu.org \ --cc=rogier.goossens@cmg.nl \ /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).