From: Andrew Haley <aph@redhat.com>
To: libffi-discuss@sourceware.org
Subject: Re: thiscall calling convention
Date: Mon, 28 Nov 2011 10:17:00 -0000 [thread overview]
Message-ID: <4ED35FA6.3080603@redhat.com> (raw)
In-Reply-To: <CADt3HYx6fDVv0+Jk30CFm+dLrGGDp8m9AZn96m=+RWcGbKMz5w@mail.gmail.com>
On 11/26/2011 07:06 AM, Federico Omoto wrote:
> Is there any plan to support the "thiscall" calling convention?
Don't we already? It's just the same as the usual convention, but
passes "this" as the first arg. Or are we talking Visual C++ ?
Andrew.
next prev parent reply other threads:[~2011-11-28 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 7:06 Federico Omoto
2011-11-28 10:17 ` Andrew Haley [this message]
2011-11-28 10:45 ` Kai Tietz
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=4ED35FA6.3080603@redhat.com \
--to=aph@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).