public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: howarth@bromo.med.uc.edu
To: gcc-gnats@gcc.gnu.org
Cc: mark@codesourcery.com
Subject: c++/10737: newer bison causes g++.dg/ parse/crash2.C to incorrectly report as failed
Date: Sun, 11 May 2003 02:46:00 -0000	[thread overview]
Message-ID: <20030511023700.14485.qmail@sources.redhat.com> (raw)


>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:


                 reply	other threads:[~2003-05-11  2:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030511023700.14485.qmail@sources.redhat.com \
    --to=howarth@bromo.med.uc.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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: link
Be 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).