public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: "Hogan, D. (GE Power & Water)" <D.Hogan@ge.com>
Cc: Alan Modra <amodra@gmail.com>, Jakub Jelinek <jakub@redhat.com>,
	       "libffi-discuss@sourceware.org"
	<libffi-discuss@sourceware.org>
Subject: Re: RFC: variadic closures in x86/x86_64
Date: Wed, 04 Dec 2013 18:51:00 -0000	[thread overview]
Message-ID: <529F7989.1050000@redhat.com> (raw)
In-Reply-To: <F023C084BCC16446BDA5B664305741E8091DD8@ALPMBAPA05.e2k.ad.ge.com>

On 12/04/2013 06:28 PM, Hogan, D. (GE Power & Water) wrote:
> On Wed, Dec 04, 2013 at 00:07:21AM, Andrew Haley wrote:

> 
>> Why do you not define a variadic C function which does this:
>>
>> void f1(int n, ...) {
>>   va_list ap;
> 
> In the libffi manual, there's a TODO about variadic closures. 

That's AFAIK to do with targets that have a different calling convention
for variadic calls.

> My interpretation of variadic closures is a closure which can access
> variadic arguments without sending in the number of arguments and
> types at the ffi_prep_cif or ffi_prep_cif_var time.  Once you have a
> variadic closure, you should be call it any number of times with any
> number of variadic arguments.

Forgive me, but that's not an answer.  I have provided an example of a
mechanism that JNA could use that would not require us to change
libffi.  Couldn't you do this in JNA?  It doesn't have to be
application-specific.

Andrew.

  reply	other threads:[~2013-12-04 18:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25  2:46 Hogan, D. (GE Power & Water)
2013-11-25  9:29 ` Andrew Haley
2013-11-25  9:37   ` Jakub Jelinek
2013-11-25 10:10     ` Andrew Haley
2013-11-26 14:27       ` Alan Modra
2013-12-04  8:03         ` Hogan, D. (GE Power & Water)
2013-12-04 11:05           ` Philip Ashmore
     [not found]             ` <F023C084BCC16446BDA5B664305741E8091E8B@ALPMBAPA05.e2k.ad.ge.com>
2013-12-05 13:03               ` Philip Ashmore
2013-12-04 12:21           ` Andrew Haley
2013-12-04 18:28             ` Hogan, D. (GE Power & Water)
2013-12-04 18:51               ` Andrew Haley [this message]
2013-12-05  0:47                 ` Hogan, D. (GE Power & Water)
2013-12-05  8:33                   ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=529F7989.1050000@redhat.com \
    --to=aph@redhat.com \
    --cc=D.Hogan@ge.com \
    --cc=amodra@gmail.com \
    --cc=jakub@redhat.com \
    --cc=libffi-discuss@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).