From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 78649 invoked by alias); 14 May 2017 10:30:36 -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 78293 invoked by uid 89); 14 May 2017 10:30:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=HTo:U*libffi-discuss, November, november, HTo:U*green X-HELO: smtp18.mail.ru Received: from smtp18.mail.ru (HELO smtp18.mail.ru) (94.100.176.155) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 14 May 2017 10:30:25 +0000 Received: from host86-128-188-209.range86-128.btcentralplus.com ([86.128.188.209]:45632 helo=sf) by smtp18.mail.ru with esmtpa (envelope-from ) id 1d9qnB-0000Fb-6i; Sun, 14 May 2017 13:30:25 +0300 Date: Sun, 14 May 2017 10:30:00 -0000 From: "Sergei Trofimovich via libffi-discuss" Reply-To: Sergei Trofimovich To: libffi-discuss@sourceware.org, Anthony Green Cc: GHC developers , Moritz Angermann Subject: Time for libffi release tarball? Message-ID: <20170514113020.0d26a0c9@sf> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/cDiz8IK_AIB5gP3.UN7vCNH"; protocol="application/pgp-signature" Authentication-Results: smtp18.mail.ru; auth=pass smtp.auth=slyfox@inbox.ru smtp.mailfrom=slyfox@inbox.ru X-7FA49CB5: 0D63561A33F958A56B7F2D79814D85D1F103DCDE96A806EDDE50DFECFCE16055725E5C173C3A84C3F4F21260D2B1B5D75CC86452CE92285C4163C681A99F5D66C4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0FF045C6A0F83C8214574AF45C6390F7469DAA53EE0834AAEE X-Mailru-Sender: 2B83DBE7458923C6AD113F5ACD3CA0042770312662773FB0EB7AC12EBE9167E07A8AF42CA9B906A5B0C293124EE1F8E466FEC6BF5C9C28D9BE1658B246A3ACF810B29241573AA60767EA787935ED9F1B X-IsSubscribed: yes X-SW-Source: 2017/txt/msg00002.txt.bz2 --Sig_/cDiz8IK_AIB5gP3.UN7vCNH Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-length: 722 Hello libffi devs! GHC (http://www.haskell.org/ghc/), a portable haskell compiler, uses libffi to implement calls into and back from C. Latest libffi-3.2.1 was released on November 12, 2014. One of problematic targets is ARMv7 iOS (clang): A few relevant commits: https://github.com/libffi/libffi/commit/bc4fc07aa58df6d7fa90b57d305d58e= ef96a0416 https://github.com/libffi/libffi/commit/e3d2812ce43940aacae5bab2d0e9652= 78cb1e7ea What do you think of releasing libffi tarball with these fixes? Would it make sense to cut libffi releases roughly at the same time major gcc releases are cut? This email is mostly the same ping from https://github.com/libffi/libffi/issues/296 Thank you! --=20 Sergei --Sig_/cDiz8IK_AIB5gP3.UN7vCNH Content-Type: application/pgp-signature Content-Description: Цифровая подпись OpenPGP Content-length: 195 -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSZKa0VG5avZRlY01hxoe52YR/zqgUCWRgxvAAKCRBxoe52YR/z qrgNAJ984O7PuRCEtOJ7ewtDhRxavZJeTACfWsaPoM5KtnzaWaVVw4X27JJ90GE= =vY1c -----END PGP SIGNATURE----- --Sig_/cDiz8IK_AIB5gP3.UN7vCNH--