From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124798 invoked by alias); 16 Nov 2015 04:27:09 -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 124781 invoked by uid 89); 16 Nov 2015 04:27:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: gproxy2-pub.mail.unifiedlayer.com Received: from gproxy2-pub.mail.unifiedlayer.com (HELO gproxy2-pub.mail.unifiedlayer.com) (69.89.18.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with SMTP; Mon, 16 Nov 2015 04:27:07 +0000 Received: (qmail 19452 invoked by uid 0); 16 Nov 2015 04:27:04 -0000 Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy2.mail.unifiedlayer.com with SMTP; 16 Nov 2015 04:27:04 -0000 Received: from box522.bluehost.com ([74.220.219.122]) by cmgw3 with id iBSt1r00H2f2jeq01BSwRY; Mon, 16 Nov 2015 04:27:02 -0700 X-Authority-Analysis: v=2.1 cv=Caqbutbl c=1 sm=1 tr=0 a=GsOEXm/OWkKvwdLVJsfwcA==:117 a=GsOEXm/OWkKvwdLVJsfwcA==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=zstS-IiYAAAA:8 a=PnD2wP_eR3oA:10 a=q5Y1GWT81MIA:10 a=qtqOOiqGOCEA:10 a=jbFG23LFyijS7dQztT8A:9 Received: from [174.16.156.173] (port=47548 helo=bapiya) by box522.bluehost.com with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1ZyBNX-00075k-Mz; Sun, 15 Nov 2015 21:26:55 -0700 From: Tom Tromey To: Tom Tromey Cc: Richard Henderson , libffi-discuss Subject: Re: documentation patch, oddities, and proposals References: <87d1vqe3e0.fsf@tromey.com> <5639B430.2010807@redhat.com> <87si4dctqh.fsf@tromey.com> Date: Mon, 16 Nov 2015 04:27:00 -0000 In-Reply-To: <87si4dctqh.fsf@tromey.com> (Tom Tromey's message of "Tue, 10 Nov 2015 16:36:22 -0700") Message-ID: <878u5ypo1h.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Identified-User: {36111:box522.bluehost.com:elynrobi:tromey.com} {sentby:smtp auth 174.16.156.173 authed with tom+tromey.com} X-SW-Source: 2015/txt/msg00099.txt.bz2 Tom> * Require each ABI to have a string name and provide a way to look up Tom> ABI by name. [...] Tom> Also, document all ABIs -- not really an ABI problem, but worth Tom> pointing out. Tom> I suppose this could be added without breaking ABI. I was taking a stab at this today but I realized I don't fully understand the PPC ABI stuff. Unlike the other ports, src/powerpc/ffitarget.h puts a bunch of flags into the ffi_abi enum. This is fine (a bit odd maybe), but what I don't know is whether all possible combinations of flags are valid. For one host: FFI_LINUX = 8, /* This and following bits can reuse FFI_COMPAT values. */ FFI_LINUX_STRUCT_ALIGN = 1, FFI_LINUX_LONG_DOUBLE_128 = 2, FFI_LINUX is required but can zero or more of the others be added in any combination? Another host: FFI_SYSV = 8, FFI_SYSV_SOFT_FLOAT = 1, FFI_SYSV_STRUCT_RET = 2, FFI_SYSV_IBM_LONG_DOUBLE = 4, FFI_SYSV_LONG_DOUBLE_128 = 16, Same question here. If they are all valid then I guess I'll need to rethink my simple naming scheme, since having 16 different multi-word ABI names seems unpleasant. Tom