From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by sourceware.org (Postfix) with ESMTPS id CE8DE3877408 for ; Thu, 1 Jul 2021 10:01:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org CE8DE3877408 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=ubuntu.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=ubuntu.com X-Envelope-From: doko@ubuntu.com Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 161A19iE004914 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 1 Jul 2021 12:01:09 +0200 To: Anthony Green , libffi-discuss References: From: Matthias Klose Subject: Re: Fwd: Announcing libffi 3.4.2 Message-ID: <4b2439f9-ecac-6c82-afad-db027825b9c6@ubuntu.com> Date: Thu, 1 Jul 2021 12:01:08 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libffi-discuss@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libffi-discuss mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2021 10:01:14 -0000 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? - README.md 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: > > 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 >