From: Michael Hope <michael.hope@linaro.org>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc@gcc.gnu.org
Subject: Re: Second GCC 4.6.0 release candidate is now available
Date: Mon, 04 Apr 2011 21:21:00 -0000 [thread overview]
Message-ID: <BANLkTik=0g7-b7LkaOeKX6zCGuxUkf7hFg@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=udjvpGe9UvemS1_73xddU=5DsWzK8POHK1=uT@mail.gmail.com>
On Sat, Mar 26, 2011 at 4:16 AM, Ramana Radhakrishnan
<ramana.gcc@googlemail.com> wrote:
> 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.
>
> These failures here
>
> For v7-a , A9 and Neon - these failures below:
>
>> Running target unix
>> FAIL: gfortran.dg/array_constructor_11.f90 -O3 -fomit-frame-pointer (test for excess errors)
>> UNRESOLVED: gfortran.dg/array_constructor_11.f90 -O3 -fomit-frame-pointer compilation failed to produce executable
>> FAIL: gfortran.dg/array_constructor_11.f90 -O3 -fomit-frame-pointer -funroll-loops (test for excess errors)
>> UNRESOLVED: gfortran.dg/array_constructor_11.f90 -O3 -fomit-frame-pointer -funroll-loops compilation failed to produce executable
>> FAIL: gfortran.dg/array_constructor_11.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions (test for excess errors)
>> UNRESOLVED: gfortran.dg/array_constructor_11.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions compilation failed to produce executable
>> FAIL: gfortran.dg/array_constructor_11.f90 -O3 -g (test for excess errors)
>> UNRESOLVED: gfortran.dg/array_constructor_11.f90 -O3 -g compilation failed to produce executable
>> FAIL: gfortran.dg/func_assign_3.f90 -O3 -fomit-frame-pointer (test for excess errors)
>> UNRESOLVED: gfortran.dg/func_assign_3.f90 -O3 -fomit-frame-pointer compilation failed to produce executable
>> FAIL: gfortran.dg/func_assign_3.f90 -O3 -fomit-frame-pointer -funroll-loops (test for excess errors)
>> UNRESOLVED: gfortran.dg/func_assign_3.f90 -O3 -fomit-frame-pointer -funroll-loops compilation failed to produce executable
>> FAIL: gfortran.dg/func_assign_3.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions (test for excess errors)
>> UNRESOLVED: gfortran.dg/func_assign_3.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions compilation failed to produce executable
>> FAIL: gfortran.dg/func_assign_3.f90 -O3 -g (test for excess errors)
>> UNRESOLVED: gfortran.dg/func_assign_3.f90 -O3 -g compilation failed to produce executable
> are caused by a broken assembler. All these tests appear to pass
> fine in a cross environment on my machine.
I've updated to binutils 2.21.51 which should fix the fault. I'm
re-running the Cortex-A9 build against the 4.6.0 release now.
> From v5t.
>
>> FAIL: gcc.dg/c90-intconst-1.c (internal compiler error)
>> FAIL: gcc.dg/c90-intconst-1.c (test for excess errors)
I re-ran this against the 4.6.0 release and these fails went away. Good.
http://gcc.gnu.org/ml/gcc-testresults/2011-04/msg00319.html
-- Michael
next prev parent reply other threads:[~2011-04-04 21:21 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
2011-04-04 21:21 ` Michael Hope [this message]
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='BANLkTik=0g7-b7LkaOeKX6zCGuxUkf7hFg@mail.gmail.com' \
--to=michael.hope@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).