From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68197 invoked by alias); 4 Nov 2015 14:20:26 -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 68167 invoked by uid 89); 4 Nov 2015 14:20:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: gproxy4-pub.mail.unifiedlayer.com Received: from gproxy4-pub.mail.unifiedlayer.com (HELO gproxy4-pub.mail.unifiedlayer.com) (69.89.23.142) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with SMTP; Wed, 04 Nov 2015 14:20:21 +0000 Received: (qmail 7262 invoked by uid 0); 4 Nov 2015 14:20:18 -0000 Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy4.mail.unifiedlayer.com with SMTP; 4 Nov 2015 14:20:17 -0000 Received: from box522.bluehost.com ([74.220.219.122]) by cmgw2 with id dSL71r00P2f2jeq01SLAx0; Wed, 04 Nov 2015 07:20:16 -0700 X-Authority-Analysis: v=2.1 cv=Jv9i8qIC 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=1RYAJFvsJAM5iCrkpqgA:9 Received: from [174.16.156.173] (port=46622 helo=pokyo) by box522.bluehost.com with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1Ztyv2-0000z3-O1; Wed, 04 Nov 2015 07:20:08 -0700 From: Tom Tromey To: Richard Henderson Cc: Tom Tromey , libffi-discuss Subject: Re: documentation patch, oddities, and proposals References: <87d1vqe3e0.fsf@tromey.com> <5639B430.2010807@redhat.com> Date: Wed, 04 Nov 2015 14:20:00 -0000 In-Reply-To: <5639B430.2010807@redhat.com> (Richard Henderson's message of "Wed, 4 Nov 2015 08:30:56 +0100") Message-ID: <87r3k526ei.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.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/msg00093.txt.bz2 >> I wasn't sure -- is this needed in some way for the closure API as >> well? If so, and someone can explain where (that is, arguments, >> return values, or both), I will write a documentation patch. rth> As far as I can tell it's just historical, and now for api rth> compatability with earlier libffi. But perhaps Anthony remembers rth> more. I also didn't check to see how the "struct { char x; }" case is handled. Does that need ffi_arg? And if so how is it unpacked? rth> Instead, have a function call taking an enumeration for the basic rth> types, as well as the abi enum. Which means that ppc can have two rth> separate structures for its longdouble, which means that both can be rth> read-only. That's what I was thinking as well. Tom