From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: laurent@guerby.net
Cc: GCC List <gcc@gcc.gnu.org>
Subject: Re: Ada ACATS Failures on SVN Trunk
Date: Fri, 14 Dec 2007 21:22:00 -0000 [thread overview]
Message-ID: <4762EB5B.7080705@oarcorp.com> (raw)
In-Reply-To: <1197663114.13773.32.camel@pc2>
Laurent GUERBY wrote:
> On Fri, 2007-12-14 at 13:41 -0600, Joel Sherrill wrote:
>
>> Laurent GUERBY wrote:
>>
>>> ACATS is clean (0 FAIL) on trunk for x86. CXF3A03 is the
>>> only FAIL for hppa-linux. c41328a is the only FAIL for powerpc64-linux.
>>> cxb3014/16 are the only FAIL on ia64-linux.
>>>
>>> You'll quickly find up to date ACATS results here:
>>>
>>> http://gcc.gnu.org/ml/gcc-testresults/2007-12/
>>>
>>>
>>>
>>>
>> Thanks Laurent. Those look much better than what I
>> am getting.
>>
>> Could this be related to PR34400?
>>
>
> 34400 is about slow compile but not about wrong code so I doubt it's the
> issue. Could you send me privately the compressed log of the ACATS run?
>
>
Sure.
> How are the other language part of the GCC testsuite doing on the
> target?
>
>
We have never figured out how to run them linking
with RTEMS. :( The last time I tried passing the extra
arguments resulted in the gcc driver core dumping.
It is on my long term wish list.
RTEMS itself was compiled with it and I don't see any
of our tests failing. Doesn't prove perfection but not
grossly broken.
> Laurent
>
> PS: I'll be travelling and be mostly offline this week-end.
>
>
Be safe.
--joel
next prev parent reply other threads:[~2007-12-14 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 19:01 Joel Sherrill
2007-12-14 19:41 ` Laurent GUERBY
2007-12-14 20:13 ` Joel Sherrill
2007-12-14 20:45 ` Laurent GUERBY
2007-12-14 21:22 ` Joel Sherrill [this message]
2007-12-14 21:36 ` Laurent GUERBY
2007-12-14 22:24 ` Joel Sherrill
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=4762EB5B.7080705@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gcc@gcc.gnu.org \
--cc=laurent@guerby.net \
/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).