public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* c/3379: gcc 3.0 gives incomprehensible error using explicit __func__
@ 2001-06-22 11:56 rogier.goossens
0 siblings, 0 replies; 4+ messages in thread
From: rogier.goossens @ 2001-06-22 11:56 UTC (permalink / raw)
To: gcc-gnats
>Number: 3379
>Category: c
>Synopsis: gcc 3.0 gives incomprehensible error using explicit __func__
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jun 22 11:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: rogier.goossens@cmg.nl
>Release: gcc 3.0
>Organization:
>Environment:
alphaev56-dec-osf4.0d
>Description:
When compiling code that explicitly declares a
(const char []) variable named __func__, gcc complains
about being confused by 'earlier' errors, and quits.
Needless to say it does not report any earlier errors.
(see instructions for repeating)
>How-To-Repeat:
Compiling the following code:
void myfun(void) {
const char __func__[] = "myfun";
}
Generates (just) the following diagnostic:
try.24.c: In function `myfun':
try.24.c:2: confused by earlier errors, bailing out
>Fix:
One fix is of course not to declare variables named
__func__. There may be others ?
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c/3379: gcc 3.0 gives incomprehensible error using explicit __func__
@ 2001-07-20 14:50 jsm28
0 siblings, 0 replies; 4+ messages in thread
From: jsm28 @ 2001-07-20 14:50 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, jsm28, nobody, rogier.goossens
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c/3379: gcc 3.0 gives incomprehensible error using explicit __func__
@ 2002-03-29 12:26 mmitchel
0 siblings, 0 replies; 4+ messages in thread
From: mmitchel @ 2002-03-29 12:26 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, jsm28, mmitchel, nobody, rogier.goossens
Synopsis: gcc 3.0 gives incomprehensible error using explicit __func__
Responsible-Changed-From-To: unassigned->mmitchel
Responsible-Changed-By: mmitchel
Responsible-Changed-When: Fri Mar 29 12:26:22 2002
Responsible-Changed-Why:
I will work on a fix.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3379
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c/3379: gcc 3.0 gives incomprehensible error using explicit __func__
@ 2002-04-03 14:21 mmitchel
0 siblings, 0 replies; 4+ messages in thread
From: mmitchel @ 2002-04-03 14:21 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, jsm28, mmitchel, rogier.goossens
Synopsis: gcc 3.0 gives incomprehensible error using explicit __func__
State-Changed-From-To: analyzed->closed
State-Changed-By: mmitchel
State-Changed-When: Wed Apr 3 14:21:08 2002
State-Changed-Why:
Already fixed in GCC 3.1.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3379
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-04-03 22:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-06-22 11:56 c/3379: gcc 3.0 gives incomprehensible error using explicit __func__ rogier.goossens
2001-07-20 14:50 jsm28
2002-03-29 12:26 mmitchel
2002-04-03 14:21 mmitchel
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).