public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Fwd: Announcing libffi 3.4.2
Date: Tue, 29 Jun 2021 17:17:18 -0400	[thread overview]
Message-ID: <CACxje5-DtjMtivhC_Q_i6E-obwg1LhrFY8aZo7762emUN+27Yw@mail.gmail.com> (raw)
In-Reply-To: <CACxje5-fo++8sksT4PMtPDa3pvB86UCKcBsc3dEM-v8cqzOPsg@mail.gmail.com>

I release 3.4.2 yesterday!  Thanks to everyone who contributed!

To be honest, with the CI infrastructure falling apart in the last few
weeks, I'm guessing we may need to make fast-following 3.4.x releases,
but we'll see.  Job number one is really moving as much CI to github
actions as quickly as possible.

I know that various Linux distro build systems are very active right
now, and I'm hopeful that we'll see this in wide usage very soon.

Thanks again,

AG

---------- Forwarded message ---------
From: Anthony Green <green@moxielogic.com>
Date: Tue, Jun 29, 2021 at 5:10 PM
Subject: Announcing libffi 3.4.2
To: <libffi-announce@sourceware.org>


I'm very pleased to announce the release of libffi version 3.4.2, which
you are free to download here:

  https://github.com/libffi/libffi/releases/download/v3.4.2/libffi-3.4.2.tar.gz

Here are some of the highlights of this release:

    3.4.2 Jun-28-21
        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.
        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.

Of particular note is Madhavan Venkataraman's static trampoline work,
as it can eliminate
the need for writeable/executable memory under certain conditions.

As usual, many thanks to all of the contributors!

Check out the following links for more details:
 https://sourceware.org/libffi
 https://github.com/libffi/libffi

Have fun!

Anthony Green
green@moxielogic.com
https://twitter.com/antgreen

       reply	other threads:[~2021-06-29 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACxje5-fo++8sksT4PMtPDa3pvB86UCKcBsc3dEM-v8cqzOPsg@mail.gmail.com>
2021-06-29 21:17 ` Anthony Green [this message]
2021-07-01 10:01   ` Matthias Klose
2021-07-02 12:25     ` 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:
  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=CACxje5-DtjMtivhC_Q_i6E-obwg1LhrFY8aZo7762emUN+27Yw@mail.gmail.com \
    --to=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).