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: Thu, 05 Dec 2013 08:33:00 -0000 [thread overview]
Message-ID: <52A03A61.1090103@redhat.com> (raw)
In-Reply-To: <F023C084BCC16446BDA5B664305741E8091E76@ALPMBAPA05.e2k.ad.ge.com>
On 12/05/2013 12:47 AM, Hogan, D. (GE Power & Water) wrote:
> I'm sure it would work. A similar suggestion is mentioned in the CFFI
> documentation. It would require a C function for every assumed
> variadic processing convention. For instance, FMI requires
> #<Type><valueReference># which is not a typical printf/logger
> convention. I didn't go down that path because I thought the manual
> was asking for patches for a different way.
>
> Thanks for the feedback.
Hmm, I'm sorry for pushing back in this way, but I think we'd need to
make the changes to all of our twenty or so back ends. And of course
no-one wants to do that.
Andrew.
prev parent reply other threads:[~2013-12-05 8:33 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
2013-12-05 0:47 ` Hogan, D. (GE Power & Water)
2013-12-05 8:33 ` Andrew Haley [this message]
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=52A03A61.1090103@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).