From: Kai Tietz <ktietz70@googlemail.com>
To: Andrew Haley <aph@redhat.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: thiscall calling convention
Date: Mon, 28 Nov 2011 10:45:00 -0000 [thread overview]
Message-ID: <CAEwic4av3CVVvKYELTiyfK+qHMuoxjaMHndqSdv9qtjOGpkXfg@mail.gmail.com> (raw)
In-Reply-To: <4ED35FA6.3080603@redhat.com>
2011/11/28 Andrew Haley <aph@redhat.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.
The "thiscall" is a a separate calling-convention for 32-bit IA
architecture, which is using just one register for passing first
argument. So don't mix it with "fastcall", which is actual passing 2
arguments in registers. You are right, that this calling-convention
is normally used only for C++ class-member functions on 32-bit IA
Windows code.
Kai
prev parent reply other threads:[~2011-11-28 10:45 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
2011-11-28 10:45 ` Kai Tietz [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=CAEwic4av3CVVvKYELTiyfK+qHMuoxjaMHndqSdv9qtjOGpkXfg@mail.gmail.com \
--to=ktietz70@googlemail.com \
--cc=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).