public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* c++/10737: newer bison causes g++.dg/ parse/crash2.C to incorrectly report as failed
@ 2003-05-11 2:46 howarth
0 siblings, 0 replies; only message in thread
From: howarth @ 2003-05-11 2:46 UTC (permalink / raw)
To: gcc-gnats; +Cc: mark
>Number: 10737
>Category: c++
>Synopsis: newer bison causes g++.dg/ parse/crash2.C to incorrectly report as failed
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun May 11 02:46:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Jack Howarth
>Release: gcc-3.3 prerelease 2 (05/09/2003)
>Organization:
>Environment:
Debian ppc sid linux
>Description:
The current debian build of gcc 3.3 prerelease 2 exposed a flaw in the g++.dg/ parse/crash2.C test when using the new bison. The results I get are posted at...
http://gcc.gnu.org/ml/gcc/2003-05/msg01030.html
and an analysis of the origin of the problem is at
http://gcc.gnu.org/ml/gcc/2003-05/msg01031.html
>How-To-Repeat:
build the current gcc-3.3_3.3ds8-0pre9 source package on debian ppc sid.
>Fix:
I am told the proper fix for this is...
Change this line:
if ('A' == x) && ('B' == y)) { } /* { dg-error "parse error" } */
to:
if ('A' == x) && ('B' == y)) { } /* { dg-error "parse|syntax error" }
*/
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-05-11 2:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-11 2:46 c++/10737: newer bison causes g++.dg/ parse/crash2.C to incorrectly report as failed howarth
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).