From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21501 invoked by alias); 18 Nov 2014 10:47:11 -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 21489 invoked by uid 89); 18 Nov 2014 10:47:11 -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:47:10 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sAIAl90c013248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 18 Nov 2014 05:47:09 -0500 Received: from pike.twiddle.home (vpn1-5-51.ams2.redhat.com [10.36.5.51]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sAIAl7f1012835 for ; Tue, 18 Nov 2014 05:47:08 -0500 Message-ID: <546B23A9.5030300@redhat.com> Date: Tue, 18 Nov 2014 10:47: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/msg00240.txt.bz2 By the by, I've been testing a merge the other direction: git://github.com/rth7680/gcc.git rth/ffi It's much less systematic than your merge this direction, and it did in fact miss that Sparc variadic patch. Curiously, there are no testsuite failures on sparc64, so there must be some test case that we're missing... r~