From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30134 invoked by alias); 18 Nov 2014 10:32:00 -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 30112 invoked by uid 89); 18 Nov 2014 10:31:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 18 Nov 2014 10:31:59 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sAIAVwL7016252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 18 Nov 2014 05:31:58 -0500 Received: from pike.twiddle.home (vpn1-5-51.ams2.redhat.com [10.36.5.51]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sAIAVtdK015931 for ; Tue, 18 Nov 2014 05:31:57 -0500 Message-ID: <546B201A.1070703@redhat.com> Date: Tue, 18 Nov 2014 10:32:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: libffi-discuss@sourceware.org Subject: Re: [PATCH 0/7] Merge of gcc patches References: <20141118101743.GA26714@linux.vnet.ibm.com> In-Reply-To: <20141118101743.GA26714@linux.vnet.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014/txt/msg00232.txt.bz2 On 11/18/2014 11:17 AM, Dominik Vogt wrote: > The following series of patches merges the changes in gcc's copy > of libffi since this gcc-commit: > > 2012-12-26 16:28 green * libffi merge > > While I've tried to resolve conflicts in a sensible way, I've not > made any effort to check what the patches do or whether they are > (still) useful, so please double check before checking in. libffi > still compiles after applying the patches 1 to 7 (without path > "0", see below), but I've not run any tests. > > The "zeroth" patch is attached right to this message. To me it > looks like a patch that is applied to gcc every time libffi is > merged, but there may be unrelated bits; I cannot judge that. (The > patch conflicts with a later patch in the series, but the conflict > is easy to resolve.) I wonder how much of this we could merge with an AM_CONDITIONAL(IN_GCC, ...) where the setting of IN_GCC of course changes between the standalone and in-tree builds. r~