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: mmitchel@codesourcery.com
Subject: objc/10739: new bison error syntax confuses objc.dg testsuite tests
Date: Sun, 11 May 2003 13:56:00 -0000	[thread overview]
Message-ID: <20030511135356.11742.qmail@sources.redhat.com> (raw)


>Number:         10739
>Category:       objc
>Synopsis:       new bison error syntax confuses objc.dg testsuite tests
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 11 13:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Jack Howarth
>Release:        gcc-3.3 prerelease (20030509)
>Organization:
>Environment:
Debian ppc sid linux with binutils 2.14.90.0.1.
>Description:
The objc.dg testsuite tests naming-1.m and naming-2.m are incorrectly being treated as failed when run against the new bison.

Executing on host: /home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/build/gcc/xgcc -B/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/build/gcc/ /home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/objc.dg/naming-1.m    -I/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/../../libobjc -L/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/build/powerpc-linux/libobjc/.libs -S  -o naming-1.s    (timeout = 300)
/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/objc.dg/naming-1.m: In function `foo':
/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/objc.dg/naming-1.m:12: error: `view' undeclared (first use in this function)
/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/objc.dg/naming-1.m:12: error: (Each undeclared identifier is reported only once
/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/objc.dg/naming-1.m:12: error: for each function it appears in.)
/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/objc.dg/naming-1.m: In function `bar':
/home/howarth/debian-gcc-3.3/gcc-3.3-3.3ds8/src/gcc/testsuite/objc.dg/naming-1.m:20: error: syntax error before '=' token
compiler exited with status 1
>How-To-Repeat:
build the current gcc-3.3-3.3ds8-pre9 package on debian sid
>Fix:
--- src/gcc/testsuite/objc.dg/naming-1.m.bak    2003-05-11 09:29:43.000000000 -0400
+++ src/gcc/testsuite/objc.dg/naming-1.m        2003-05-11 09:30:26.000000000 -0400
@@ -17,5 +17,5 @@
 void bar(void)
 {
        View *view;     /* ok */
-       View = 1;       /* { dg-error "parse error" } */
+       View = 1;       /* { dg-error "parse|syntax error" } */
 }
--- src/gcc/testsuite/objc.dg/naming-2.m.bak    2003-05-11 09:50:16.000000000 -0400
+++ src/gcc/testsuite/objc.dg/naming-2.m        2003-05-11 09:32:35.000000000 -0400
@@ -4,7 +4,7 @@
   
 @interface Foo
 @end
-float Foo;  /* { dg-error "parse error before" } */
+float Foo;  /* { dg-error "parse|syntax error before" } */
   
 double Bar;
 @interface Bar
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-05-11 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 13:56 howarth [this message]
2003-05-11 14:10 steven

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=20030511135356.11742.qmail@sources.redhat.com \
    --to=howarth@bromo.med.uc.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=mmitchel@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).