public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Nicola Pero" <nicola.pero@meta-innovation.com>
To: "Ramana Radhakrishnan" <ramana.gcc@googlemail.com>
Cc: "Michael Hope" <michael.hope@linaro.org>,
	"Jakub Jelinek" <jakub@redhat.com>,
	gcc@gcc.gnu.org
Subject: Re: Second GCC 4.6.0 release candidate is now available
Date: Fri, 25 Mar 2011 18:03:00 -0000	[thread overview]
Message-ID: <1301075632.321822606@192.168.4.58> (raw)
In-Reply-To: <AANLkTi=udjvpGe9UvemS1_73xddU=5DsWzK8POHK1=uT@mail.gmail.com>


> Hi Michael,
>
> Thanks for running these. I spent some time this morning looking
> through the results, they largely look ok though I don't have much
> perspective on the the objc/ obj-c++ failures.

I had a quick look at the test results for 4.6.0 under Michael's
name on the mailing list.

The ObjC failures

FAIL: objc.dg-struct-layout-encoding-1/t025_main.m execution test
FAIL: objc.dg-struct-layout-encoding-1/t027_main.m execution test
FAIL: objc.dg-struct-layout-encoding-1/t028_main.m execution test
FAIL: objc.dg-struct-layout-encoding-1/t029_main.m execution test
FAIL: objc.dg-struct-layout-encoding-1/t030_main.m execution test
FAIL: objc.dg-struct-layout-encoding-1/t031_main.m execution test

are not worrying.  These fail on many platforms (where they are
marked as xfails).

But, in http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg02391.html
a number of ObjC PCH failures are reported; but then lots of PCH
tests in the same report fail for C too, so it doesn't seem to be
anything specific to ObjC.

So, as far as I can see, ObjC/ObjC++ looks good. :-)

Thanks

  reply	other threads:[~2011-03-25 17:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 17:22 Jakub Jelinek
2011-03-21 22:13 ` Second " Jakub Jelinek
2011-03-24 22:58   ` Michael Hope
2011-03-25 15:47     ` Ramana Radhakrishnan
2011-03-25 18:03       ` Nicola Pero [this message]
2011-04-04 21:21       ` Michael Hope
2011-03-25 17:37   ` Joe Buck
2011-03-25 17:50     ` Jakub Jelinek

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=1301075632.321822606@192.168.4.58 \
    --to=nicola.pero@meta-innovation.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=michael.hope@linaro.org \
    --cc=ramana.gcc@googlemail.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).