From: Alan Hourihane <alanh@fairlite.co.uk>
To: libffi-discuss@sourceware.org
Subject: Re: libffi 3.0.14-rc0 needs testing!
Date: Wed, 05 Mar 2014 00:31:00 -0000 [thread overview]
Message-ID: <53167059.2030002@fairlite.co.uk> (raw)
In-Reply-To: <CANu=DmiD-J+2ivEsaSMKvTMXK96V+0gc1LZNOjextNswiMiJLA@mail.gmail.com>
On 03/04/14 07:29, Will Newton wrote:
> On 2 March 2014 07:48, Anthony Green <green@moxielogic.com> wrote:
>> Hello -
>>
>> I would really appreciate some feedback on 3.0.14-rc0, which you can
>> download from here:
>>
>> ftp://sourceware.org/pub/libffi/libffi-3.0.14-rc0.tar.gz
>>
>> I've changed my mind, and will continue using the wiki to track test
>> results. Feel free to post them yourself, or send me a note and I'll
>> update the table.
>>
>> http://moxielogic.org/wiki/libffi-3.0.14
> Results for armv7l-unknown-linux-gnueabihf (gcc 4.6.3, binutils 2.22):
>
> === libffi Summary ===
>
> # of expected passes 1819
> # of unsupported tests 55
>
Same here for m68k-atari-mint...
=== libffi Summary ===
# of expected passes 1819
# of unsupported tests 55
Alan.
next prev parent reply other threads:[~2014-03-05 0:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 23:49 Anthony Green
2014-03-01 23:56 ` Anthony Green
2014-03-03 12:44 ` Dominik Vogt
2014-03-03 19:17 ` David Fang
2014-03-04 7:29 ` Will Newton
2014-03-05 0:31 ` Alan Hourihane [this message]
2014-03-04 22:14 ` Matthias Klose
2014-03-25 21:11 ` libffi 3.1-rc1 " Anthony Green
2014-03-27 12:23 ` Dominik Vogt
2014-03-27 12:25 ` Dominik Vogt
2014-03-27 12:31 ` Dominik Vogt
2014-03-27 12:40 ` Samuli Suominen
2014-03-27 12:45 ` Samuli Suominen
2014-03-27 12:55 ` Samuli Suominen
2014-03-28 15:43 ` Anthony Green
2014-03-28 15:05 ` James Greenhalgh
2014-03-28 17:33 ` Anthony Green
2014-04-24 12:47 ` Marcus Shawcroft
2014-03-28 20:37 ` Andreas Tobler
2014-03-28 20:39 ` Matthias Klose
2014-03-28 21:56 ` Anthony Green
2014-03-28 22:31 ` Anthony Green
2014-03-29 14:25 ` ABI breakage (Was: libffi 3.1-rc1 needs testing!) Anthony Green
2014-05-30 12:21 ` Matthias Klose
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=53167059.2030002@fairlite.co.uk \
--to=alanh@fairlite.co.uk \
--cc=libffi-discuss@sourceware.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).