public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/34310]  New: new objc testsuite failures from "expected ';' before '__attribute__'" under darwin9
Date: Sat, 01 Dec 2007 20:32:00 -0000	[thread overview]
Message-ID: <bug-34310-11113@http.gcc.gnu.org/bugzilla/> (raw)

When built under Darwin9, the objc testsuite exhibits a number of regressions
compared to Darwin8 due to compilation errors of "expected ';' before
'__attribute__'". These new failures include...

objc/execute/bycopy-1.m compilation
objc/execute/bycopy-2.m compilation
objc/execute/bycopy-3.m compilation
objc/execute/formal_protocol-5.m compilation
objc/execute/formal_protocol-6.m compilation
objc/execute/formal_protocol-7.m compilation
objc/execute/np-1.m compilation
objc/execute/np-2.m compilation
objc/execute/protocol-isEqual-1.m compilation
objc/execute/protocol-isEqual-2.m compilation
objc/execute/protocol-isEqual-3.m compilation
objc/execute/protocol-isEqual-4.m compilation
objc.dg/encode-3.m (test for excess errors)
objc.dg/headers.m (test for excess errors)
objc.dg/method-6.m (test for excess errors)
objc.dg/no-extra-load.m (test for excess errors)
objc.dg/proto-lossage-3.m (test for excess errors)
objc.dg/proto-qual-1.m (test for excess errors)

All of these errors are of the form...

In file included from
/sw/src/fink.build/gcc43-4.2.999-20071130/gcc-4.3-20071130/gcc/testsuite/objc/execute/bycopy-1
.m:7:
/usr/include/objc/Protocol.h:46: error: expected ';' before '__attribute__'
/usr/include/objc/Protocol.h:50: error: expected ';' before '__attribute__'
/usr/include/objc/Protocol.h:54: error: expected ';' before '__attribute__'
/usr/include/objc/Protocol.h:55: error: expected ';' before '__attribute__'
compiler exited with status 1
output is:
In file included from
/sw/src/fink.build/gcc43-4.2.999-20071130/gcc-4.3-20071130/gcc/testsuite/objc/execute/bycopy-1
.m:7:
/usr/include/objc/Protocol.h:46: error: expected ';' before '__attribute__'
/usr/include/objc/Protocol.h:50: error: expected ';' before '__attribute__'
/usr/include/objc/Protocol.h:54: error: expected ';' before '__attribute__'
/usr/include/objc/Protocol.h:55: error: expected ';' before '__attribute__'

FAIL: objc/execute/bycopy-1.m compilation,  -O0  -fnext-runtime


-- 
           Summary: new objc testsuite failures from "expected ';' before
                    '__attribute__'" under darwin9
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: objc
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: howarth at nitro dot med dot uc dot edu
  GCC host triplet: powerpc-apple-darwin9


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34310


             reply	other threads:[~2007-12-01 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01 20:32 howarth at nitro dot med dot uc dot edu [this message]
2008-09-16 14:43 ` [Bug objc/34310] " dominiq at lps dot ens dot fr
2008-09-16 22:23 ` dominiq at lps dot ens dot fr
2008-09-16 22:24 ` dominiq at lps dot ens dot fr
2008-09-16 22:31 ` [Bug objc/34310] Attribute support for method pinskia at gcc dot gnu dot org

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=bug-34310-11113@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).