From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10742 invoked by alias); 11 Nov 2014 14:59:16 -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 10641 invoked by uid 89); 11 Nov 2014 14:59:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: cam-smtp0.cambridge.arm.com Received: from fw-tnat.cambridge.arm.com (HELO cam-smtp0.cambridge.arm.com) (217.140.96.21) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 11 Nov 2014 14:59:14 +0000 Received: from arm.com (e106375-lin.cambridge.arm.com [10.1.203.34]) by cam-smtp0.cambridge.arm.com (8.13.8/8.13.8) with ESMTP id sABEx9wD020327; Tue, 11 Nov 2014 14:59:09 GMT Date: Tue, 11 Nov 2014 14:59:00 -0000 From: James Greenhalgh To: Anthony Green Cc: "libffi-discuss@sourceware.org" Subject: Re: libffi 3.2 and disruptive changes Message-ID: <20141111145909.GA8500@arm.com> References: <87wq71yej4.fsf@moxielogic.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87wq71yej4.fsf@moxielogic.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2014/txt/msg00212.txt.bz2 On Tue, Nov 11, 2014 at 02:53:35PM +0000, Anthony Green wrote: > > I'd like to move ahead with Richard's proposed changes for GO, complex > types, and the numerous other clean ups he's proposed. > > These changes will break msvc builds as well as iOS/OSX. > > As long as we're breaking things, I'd like to use this opportunity to > change the header files so we have a shared set of .h files in > /usr/include. > > Once things settle down from these changes, I'm hoping somebody can help > with the msvc and iOS/OSX ports. > > In preparation for all of these changes, I've made a quick 3.2 release. > There were a few nice fixes that were sitting around in the tree, and > I'm not sure how long this next round of hacking will take. > > The 3.2 release should be in pretty good shape *except* for the win32/64 > msvc builds which are known to be broken. See > https://github.com/atgreen/libffi/issues/138 for details. AArch64 linux builds are still broken (Alan Lawrence posted a patch at https://sourceware.org/ml/libffi-discuss/2014/msg00091.html ) Could we please have that patch in for the 3.2 release? Thanks, James