From: David Gilbert <david.gilbert@linaro.org>
To: Anthony Green <green@moxielogic.com>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: libffi 3.0.11 release candidate 2 available for testing
Date: Fri, 18 Nov 2011 12:09:00 -0000 [thread overview]
Message-ID: <CA+1XiSf6fT+-bggaLPiPS+oTYWvqk+hkQ6sXERSfEy3U7ApdSQ@mail.gmail.com> (raw)
In-Reply-To: <4EBF4D9E.9020409@moxielogic.com>
On 13 November 2011 04:54, Anthony Green <green@moxielogic.com> wrote:
> I've just uploaded libffi 3.0.11rc2 for testing here:
> ftp://sourceware.org/pub/libffi/libffi-3.0.11-rc2.tar.gz
>
> I bumped the sonumber for 3.0.11 because it contains two ABI changes...
>
> 1) a debug function was removed from the non-debug builds
>
> 2) this test release includes David Gilbert's changes to support variadic
> functions.
Hi Anthony,
Thanks for that - but it looks like a small chunk is missing from
one of the test cases:
On armhf I'm getting:
FAIL: libffi.call/cls_double_va.c -O0 -W -Wall output pattern test, is 7.0
res: 4
2.6
res: 4
? should match 7.0
?es: 4
?.0
res: 4
and looking at cls_double_va.c it's missing the chunk:
@@ -48,6 +48,10 @@ int main (void)
printf("res: %d\n", (int) res);
// { dg-output "\nres: 4" }
+ /* The call to cls_double_va_fn is static, so have to use a
normal prep_cif */
+ CHECK(ffi_prep_cif(&cif, FFI_DEFAULT_ABI, 2, &ffi_type_sint,
+ arg_types) == FFI_OK);
+
CHECK(ffi_prep_closure_loc(pcl, &cif, cls_double_va_fn, NULL,
code) == FFI_OK);
res = ((int(*)(char*, double))(code))(format, doubleArg);
that was in my patch; the failures go away with that.
(We also get XPASS: libffi.call/cls_longdouble.c which I think is an
old one, just with it not
knowing it will work on modern ARM - that's both arm and armhf)
Dave (away for the next week)
next prev parent reply other threads:[~2011-11-18 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 4:55 Anthony Green
2011-11-13 12:45 ` Timothy Wall
2011-11-13 13:29 ` Mark Wielaard
2011-11-18 12:09 ` David Gilbert [this message]
2011-11-18 16:13 ` Anthony Green
2011-11-18 7:54 Peter Kruse
2011-11-18 15:42 ` Anthony Green
2011-11-23 8:39 ` Peter Kruse
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=CA+1XiSf6fT+-bggaLPiPS+oTYWvqk+hkQ6sXERSfEy3U7ApdSQ@mail.gmail.com \
--to=david.gilbert@linaro.org \
--cc=green@moxielogic.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).