public inbox for
 help / color / mirror / Atom feed
From: Anthony Green <>
To: libffi-discuss <>
Subject: Re: Please help prep for a new libffi release
Date: Sun, 18 Sep 2022 18:25:26 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

I spent some time trying to fix the 32-bit x86 results.  As it
happens, libffi is doing things mostly right.  It's GCC that can't
return small structs (<= 16 byte) properly for any of the MS ABIs.
I'm just going to ignore this for now and force the CI tests to pass
with new rlgl policy.

I'll probably spin out the new release in the next day or two.  As far
as I can tell there are no regressions.

These are the highlights:

        All struct args are passed by value, regardless of size, as per ABIs.
        Enable static trampolines for Cygwin.
        Add support for Loongson's LoonArch64 architecture.
        Fix x32 static trampolines.
        Fix 32-bit x86 stdcall stack corruption.
        Fix ILP32 aarch64 support.


On Mon, Sep 12, 2022 at 10:19 AM Anthony Green <> wrote:
> On Wed, Sep 7, 2022 at 9:44 AM Anthony Green <> wrote:
> >
> >  the Cygwin results are a mess
> I fixed this porting static trampolines to Cygwin.  Cygwin emulates
> Linux enough (eg. /proc filesystem), that turning on static
> trampolines was easy.  The Cygwin results are pretty clean now.
> AG

      reply	other threads:[~2022-09-18 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 13:44 Anthony Green
2022-09-12 14:19 ` Anthony Green
2022-09-18 22:25   ` Anthony Green [this message]

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