From: David Gilbert <david.gilbert@linaro.org>
To: Anthony Green <green@redhat.com>
Cc: Chung-Lin Tang <cltang@linaro.org>,
libffi-discuss@sourceware.org, Marcus.Shawcroft@arm.com
Subject: Re: [PATCH] Add variadic support
Date: Mon, 28 Feb 2011 09:08:00 -0000 [thread overview]
Message-ID: <AANLkTi=ttAc32uYM-4pLB+WUMCF5TsZAsg85xL=ARB0a@mail.gmail.com> (raw)
In-Reply-To: <m3wrkodjit.fsf@redhat.com>
On 25 February 2011 19:03, Anthony Green <green@redhat.com> wrote:
> Chung-Lin Tang <cltang@linaro.org> writes:
>> Anthony, as maintainer, do you have any ideas?
>>
>
> I always envisioned it working this way:
>
> - add a new FFI type, say FFI_TYPE_VARIADIC
> - users would just append this to the array of types when they
> create a cif for a variadic function
>
> No new API is required in this case. Wouldn't this work?
I think my main reason against that was it would require every backend
to be modified
to skip it (and skip a hole in the values array).
Dave
next prev parent reply other threads:[~2011-02-28 9:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:41 Dr. David Alan Gilbert
2011-02-23 12:39 ` Anthony Green
2011-02-23 13:12 ` David Gilbert
2011-02-23 13:26 ` Chung-Lin Tang
2011-02-23 16:20 ` David Gilbert
2011-02-23 16:56 ` Chung-Lin Tang
2011-02-23 17:21 ` David Gilbert
2011-02-23 17:39 ` Chung-Lin Tang
2011-02-24 6:37 ` Chung-Lin Tang
2011-02-25 12:56 ` David Gilbert
2011-02-25 13:23 ` Chung-Lin Tang
2011-02-25 19:02 ` Anthony Green
2011-02-28 9:08 ` David Gilbert [this message]
2011-03-07 18:19 ` David Gilbert
2011-03-16 9:52 ` Chung-Lin Tang
2011-03-16 14:12 ` Anthony Green
2011-03-16 14:25 ` David Gilbert
2011-02-23 21:16 ` PowerPC failures (Was: [PATCH] Add variadic support) Anthony Green
2011-02-24 10:43 ` David Gilbert
2011-02-24 22:37 ` PowerPC failures Anthony Green
2011-02-24 22:41 ` Matthias Klose
2011-02-25 19:18 ` Anthony Green
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='AANLkTi=ttAc32uYM-4pLB+WUMCF5TsZAsg85xL=ARB0a@mail.gmail.com' \
--to=david.gilbert@linaro.org \
--cc=Marcus.Shawcroft@arm.com \
--cc=cltang@linaro.org \
--cc=green@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).