From: Matthias Klose <doko@ubuntu.com>
To: libffi-discuss@sourceware.org
Subject: Re: libffi 3.0.14-rc0 needs testing!
Date: Tue, 04 Mar 2014 22:14:00 -0000 [thread overview]
Message-ID: <53165052.1050707@ubuntu.com> (raw)
In-Reply-To: <87eh2liiow.fsf@moxielogic.com>
Am 02.03.2014 00:48, schrieb Anthony Green:
>
> 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 don't see any test regressions or test failures on armhf, arm64, i386, amd64,
kfreebsd-amd64, s390x, powerpc, sparc, ppc64el. Other builds are not yet started.
However there are some symbols changes on armhf:
- ffi_closure_SYSV_inner@Base 3.0.4
+#MISSING: 3.0.14~rc0-1# ffi_closure_SYSV_inner@Base 3.0.4
- ffi_prep_args@Base 3.0.4
+#MISSING: 3.0.14~rc0-1# ffi_prep_args@Base 3.0.4
+ ffi_prep_args_SYSV@Base 3.0.14~rc0-1
+ ffi_prep_args_VFP@Base 3.0.14~rc0-1
are these expected?
Matthias
next prev parent reply other threads:[~2014-03-04 22:14 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
2014-03-04 22:14 ` Matthias Klose [this message]
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=53165052.1050707@ubuntu.com \
--to=doko@ubuntu.com \
--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).