From: Florian Weimer <fweimer@redhat.com>
To: Martin Uecker <ma.uecker@gmail.com>
Cc: Martin Uecker via Libffi-discuss <libffi-discuss@sourceware.org>,
Anthony Green <green@moxielogic.com>
Subject: Re: wide function pointer type
Date: Tue, 19 Oct 2021 12:15:00 +0200 [thread overview]
Message-ID: <87o87lfhi3.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <6a0299e6b3c47cddd88b24d569fca8aeb4717aeb.camel@gmail.com> (Martin Uecker's message of "Tue, 19 Oct 2021 11:43:52 +0200")
* Martin Uecker:
>> For GCC's nested function extension, there are no ABI concerns
>> because the nested function definition and the thunk generation are
>> always built from the same translation unit. So GCC can just pick a
>> custom calling convention, similar to what it does for other local,
>> non-escaping functions.
>
> Yes, but there are many other languages that make use of the
> static chain. So it would be good to have a standardized ABI
> for this.
What's the exact use case for this? These other languages do not
usually have stable ABIs that inter-operate across different
implementations.
Thanks,
Florian
next prev parent reply other threads:[~2021-10-19 10:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 11:32 Martin Uecker
2021-10-17 23:35 ` Anthony Green
2021-10-18 5:33 ` Martin Uecker
2021-10-18 5:58 ` Martin Uecker
2021-10-18 7:36 ` Florian Weimer
2021-10-18 7:56 ` Martin Uecker
2021-10-19 9:22 ` Florian Weimer
2021-10-19 9:43 ` Martin Uecker
2021-10-19 10:15 ` Florian Weimer [this message]
2021-10-19 12:13 ` Martin Uecker
2021-10-20 8:24 ` Kaz Kylheku (libffi)
2021-10-20 18:52 ` Martin Uecker
2021-10-20 9:10 ` Florian Weimer
2021-10-20 9:21 ` Martin Uecker
2021-10-20 9:27 ` Florian Weimer
2021-10-20 17:27 ` Kaz Kylheku (libffi)
2021-10-21 9:48 ` Florian Weimer
2021-10-10 17:01 Kaz Kylheku (libffi)
2021-10-10 17:44 ` Martin Uecker
2021-10-10 17:49 ` Daniel Colascione
2021-10-10 18:05 ` Martin Uecker
2021-10-10 18:17 ` Daniel Colascione
2021-10-10 18:47 ` Martin Uecker
2021-10-10 18:57 ` Daniel Colascione
2021-10-10 19:24 ` Martin Uecker
2021-10-16 8:08 ` Jarkko Hietaniemi
2021-10-16 9:35 ` Jarkko Hietaniemi
2021-10-10 18:31 ` Kaz Kylheku (libffi)
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=87o87lfhi3.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=ma.uecker@gmail.com \
/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).