This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
c++/10737: newer bison causes g++.dg/ parse/crash2.C to incorrectly report as failed
- From: howarth at bromo dot med dot uc dot edu
- To: gcc-gnats at gcc dot gnu dot org
- Cc: mark at codesourcery dot com
- Date: 11 May 2003 02:37:00 -0000
- Subject: c++/10737: newer bison causes g++.dg/ parse/crash2.C to incorrectly report as failed
- Reply-to: howarth at bromo dot med dot uc dot edu
>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: