public inbox for
 help / color / mirror / Atom feed
From: Jeremy Huddleston Sequoia <>
To: Anthony Green <>
Cc: libffi-discuss <>,
Subject: Re: Aiming for a libffi release in the next two weeks
Date: Sat, 26 Jun 2021 12:59:19 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hey Anthony,

Sorry about missing the original email.  I was out for my anniversary that week. =)

I'd say that Apple Silicon support is still not fully there yet.  Most of the Apple Silicon changes are in, but we still have one left. We need to finish upstreaming the trampoline dylib (  There was a bit of divergence between our branch and mainline a couple months ago which made this a bit tricky.  I think I started looking into it around April but had to shelve it due to WWDC prep.  I'll try to get to it at some point in the next month or so.

> On Jun 26, 2021, at 09:19, Anthony Green <> wrote:
> I've just published libffi 3.4 release candidate 1.  You can download and test from here:
> <>
> I'd appreciate any feedback and hope to make the final release on Monday at the latest.
> AG
> On Tue, Jun 15, 2021 at 3:50 PM Anthony Green < <>> wrote:
> DJ brought to my attention the fact that we'll be missing important release windows for Fedora and downstream distros if we don't get something out the door in the next two weeks.  And I'm very excited about the improvements targeted for this release -- Madhavan's static trampoline work in particular.
> There are a number of PR and Issues that have been sitting around for a while.  Please bump them if you think they are important.
> One area I'd like some clarity on is "apple silicon" support.  Not being a Mac user, I'm looking at Apple and Jeremy Huddleston Sequoia for guidance here.  There's a big PR WIP sitting on github.
> Also.. travis-ci testing for MacOS hasn't been working for a long time thanks to homebrew timeouts.  Something got really slow here.   Does anybody have insight into this?
> As always, thank you for your contributions and patience.  Big shout out to DJ for his recent efforts.
> AG
> In the queue for 3.4...
>         Add static trampoline support for Linux on x86_64 and ARM64.
>         Add support for Alibaba's CSKY architecture.
>         Add support for Kalray's KVX architecture.
>         Add support for Intel Control-flow Enforcement Technology (CET).
>         Add support for ARM Pointer Authentication (PA).
>         Fix 32-bit PPC regression.
>         Fix MIPS soft-float problem.
>         Fox x86-64 nested struct varargs passing problem.
>         Enable tmpdir override with the $LIBFFI_TMPDIR environment variable.
>         Enable compatibility with MSVC runtime stack checking.
>         Reject float and small integer argument in ffi_prep_cif_var().
>           Callers must promote these types themselves.

  reply	other threads:[~2021-06-26 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 19:50 Anthony Green
2021-06-15 19:52 ` Jeff Law
2021-06-26 16:19 ` Anthony Green
2021-06-26 19:59   ` Jeremy Huddleston Sequoia [this message]
2021-06-26 20:13     ` Anthony Green
2021-06-28 14:09   ` Anthony Green

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).