From: Anthony Green <green@moxielogic.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: libffi-discuss@sourceware.org,
David Gilbert <david.gilbert@linaro.org>,
GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: Please help test libffi 3.0.11-rc3
Date: Fri, 06 Apr 2012 21:02:00 -0000 [thread overview]
Message-ID: <CACxje59J6pSHYsiZwNCM=AOix9FpOv9U+o1J0Rjkmp=_uH=kqg@mail.gmail.com> (raw)
In-Reply-To: <4F7F5233.7060508@ubuntu.com>
On Fri, Apr 6, 2012 at 4:29 PM, Matthias Klose <doko@ubuntu.com> wrote:
> I see that some of the armhf-variadic patches are not applied, attached.
> Please could you confirm if dropping these changes is deliberate?
Could you please double check this? I see that the two test case
tweaks are missing, but the third patch fragment seems wrong.
src/arc/ffi.c does include ffi_prep_cif_machdep_var().
AG
next prev parent reply other threads:[~2012-04-06 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACxje586xNJF1J4mOZeqD9HCUbuR7iK6Eb+dtYCUEZ3y12zagA@mail.gmail.com>
2012-04-06 20:30 ` Matthias Klose
2012-04-06 21:02 ` Anthony Green [this message]
2012-04-07 11:29 ` 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='CACxje59J6pSHYsiZwNCM=AOix9FpOv9U+o1J0Rjkmp=_uH=kqg@mail.gmail.com' \
--to=green@moxielogic.com \
--cc=david.gilbert@linaro.org \
--cc=doko@ubuntu.com \
--cc=java-patches@gcc.gnu.org \
--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).