public inbox for
 help / color / mirror / Atom feed
From: Matthias Klose <>
To: Anthony Green <>,
	libffi-discuss <>
Subject: Re: Fwd: Announcing libffi 3.4.2
Date: Thu, 1 Jul 2021 12:01:08 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Anthony,

In February 2020, you asked in the thread "Another libffi ABI change and another
release" about a new release. Pings in July 2020 and November were unanswered.
3.3 had a similar release process, with a pending release for more than two
years. Now rushing a new release just for the sake of a single distro seems odd,
maybe there is some room for improvement in the release process?

When looking at 3.4.2 (after announcing 3.4),

 - libtool-version says the abi version is 9, but that seems
   to be ignored. Where is the definition of the ABI version
   coming from?

 - talks about 3.4.1, not 3.4.2.

I packaged 3.4.2 for Debian (the only way I can test it on the Debian
infrastructure), it needs manual approval for the renamed library package, so I
can't give feedback on test results yet, and have to wait until its built.
Tests for the Ubuntu architectures pass.

Do you plan to update the libffi copy within GCC to this release?   If not,
could you give instructions, how the two copies are managed in your VCS, and
what is the best way to merge those?

I just saw your ping on #libffi on Freenode on Monday, however you are seldom be
present on this channel.  Is this channel still somewhat official, Is it moved
to Libera.Net as everything else?  If yes, maybe mention the channel on the
libffi home page as well.

Thanks, Matthias

On 6/29/21 11:17 PM, Anthony Green wrote:
> 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 <>
> Date: Tue, Jun 29, 2021 at 5:10 PM
> Subject: Announcing libffi 3.4.2
> To: <>
> I'm very pleased to announce the release of libffi version 3.4.2, which
> you are free to download here:
> 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:
> Have fun!
> Anthony Green

  reply	other threads:[~2021-07-01 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-06-29 21:17 ` Anthony Green
2021-07-01 10:01   ` Matthias Klose [this message]
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:

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