From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 105332 invoked by alias); 15 May 2017 17:34:23 -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 105321 invoked by uid 89); 15 May 2017 17:34:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=agreen, october, October, HTo:U*libffi-discuss X-HELO: einhorn-mail.in-berlin.de Received: from einhorn-mail.in-berlin.de (HELO einhorn-mail.in-berlin.de) (217.197.80.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 15 May 2017 17:34:21 +0000 X-Envelope-From: doko@ubuntu.com Received: from [10.0.1.31] (c-24-21-112-64.hsd1.or.comcast.net [24.21.112.64]) (authenticated bits=0) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id v4FHX3Dw027969 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 May 2017 19:33:05 +0200 Subject: Re: Time for libffi release tarball? To: Sergei Trofimovich , libffi-discuss@sourceware.org, Anthony Green References: <20170514113020.0d26a0c9@sf> Cc: GHC developers , Moritz Angermann From: Matthias Klose Message-ID: <1bd1cd4d-0a88-de8c-8d33-82d3b87146e8@ubuntu.com> Date: Mon, 15 May 2017 17:34:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170514113020.0d26a0c9@sf> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017/txt/msg00003.txt.bz2 On 14.05.2017 03:30, Sergei Trofimovich via libffi-discuss wrote: > 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/bc4fc07aa58df6d7fa90b57d305d58eef96a0416 > https://github.com/libffi/libffi/commit/e3d2812ce43940aacae5bab2d0e965278cb1e7ea > > 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! Two days ago, I did a libffi trunk test build, see https://buildd.debian.org/status/package.php?p=libffi&suite=experimental found a regression building on x86_64-linux-gnux32 (see issue #306). Yes, I think a release is really needed, but unfortunately there was no feedback since my last question from October 2016. There is the #libffi channel on Freenode as well, but I didn't see agreen there either for a long time. Matthias