From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15656 invoked by alias); 24 Dec 2014 16:31:24 -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 15643 invoked by uid 89); 24 Dec 2014 16:31:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 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; Wed, 24 Dec 2014 16:31:20 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sBOGVFC7023481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 24 Dec 2014 11:31:15 -0500 Received: from anchor.twiddle.net (vpn-225-109.phx2.redhat.com [10.3.225.109]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sBOGVEnj030132; Wed, 24 Dec 2014 11:31:14 -0500 Message-ID: <549AEA51.2000500@redhat.com> Date: Wed, 24 Dec 2014 16:31:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: u-xsnf@aetey.se, libffi-discuss@sourceware.org Subject: Re: showstopper bug on x86 (Re: libffi does not follow proper ABI on ia32) References: <20141222193538.GW14316@example.net> <20141224135825.GF14316@example.net> In-Reply-To: <20141224135825.GF14316@example.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014/txt/msg00288.txt.bz2 On 12/24/2014 05:58 AM, u-xsnf@aetey.se wrote: > Nevertheless I would appreciate at least hints about the prospect to fix > this bug (apparently non-conformant C ABI of libffi on x86 Linux), > which presumably went unnoticed for a long time due to gcc not exercising > the full ABI. Yes, I see the problem. Fixing it may have to wait until the new year. r~