From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37799 invoked by alias); 19 Sep 2019 18:29:53 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 37790 invoked by uid 89); 19 Sep 2019 18:29:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=hes, dj, Fedora, he's X-HELO: mail-lf1-f53.google.com Received: from mail-lf1-f53.google.com (HELO mail-lf1-f53.google.com) (209.85.167.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Sep 2019 18:29:51 +0000 Received: by mail-lf1-f53.google.com with SMTP id d17so3100594lfa.7 for ; Thu, 19 Sep 2019 11:29:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=moxielogic-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=NKmqoifYSidwPQv3QZxBfhhSd6zocxPt4Dad1RkcoZA=; b=a+gpHxKJlYCppkldCkcIaGQ90/uZAJNgNy4ZruBmLrCtMTxzzi4edws9cO7OYSOWje fRvvEFmuP7rkPSj28JwgywlPJrLF9xc/4aRyk+flH/G8OEWRNvwEdtqhTl+LaPkQouAS +qMVyzvdJAeGaHssd6UMTqz1RxLitIx0Ulnc5I7xqa1A4OJFR2M1t0mji3jrvYZvaucn hITNYANgNJjiVmb2SnC86o9aXjrRzu9eUsbZhVDxRZ+FqexYhfn+GQVpk65MYCx8DXm8 uIVDsSjjLOellWh2KTdUOoYx7uHcCmxKhR+WPwDMx6aOUSlF67Yo0SYBMzMi02YN986Z hMLQ== MIME-Version: 1.0 From: Anthony Green Date: Thu, 19 Sep 2019 18:29:00 -0000 Message-ID: Subject: Some libffi updates To: libffi-discuss Cc: DJ Delorie , fweimer@redhat.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00032.txt.bz2 Yesterday, in Montreal, DJ Delorie, Florian Weimer and I had a little libffi meeting ... A new libffi release was the #1 topic. My main concern here is making sure we haven't broken the ABI since the last release. DJ pointed out that we can use libabigail ( https://sourceware.org/libabigail/ ) as part of the build/CI process , comparing the output to the current Fedora libffi (for instance). I believe that he's going to try to make this happen. I think the only Travis CI failure right now is related to apt-get refusing to pull moxie toolchain packages from an insecure (http-only) repo. I'm just going to let's-encrypt up some certs to fix that soon. I haven't checked the appveyor results in a while. The second topic was related to an idea Florian had to eliminate the need for RWX memory or the selinux hacks on x86 Linux. It seems like a great idea, and I hope we'll see patches sometime in the future. In addition, as a result of this meeting, I have enabled libffi repo commit access for DJ. Thanks for your help DJ! AG