From: DJ Delorie <dj@redhat.com>
To: Anthony Green <green@moxielogic.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: Change in libffi behaviour -- large struct args
Date: Tue, 31 May 2022 11:53:41 -0400 [thread overview]
Message-ID: <xn1qw9snp6.fsf@greed.delorie.com> (raw)
In-Reply-To: <CACxje5_m_6U0UyQYeo7p6+TRtybAE7LdovUUTvP6yGH0QV6YEw@mail.gmail.com>
While this is technically an ABI change, if the "old" ABI never worked,
I can't see how this would break anything by changing.
I will add that passing structs is likely more complex than you think ;-)
next prev parent reply other threads:[~2022-05-31 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 13:40 Anthony Green
2022-05-28 15:38 ` dancol
2022-05-28 15:50 ` Anthony Green
2022-05-29 14:09 ` Anthony Green
2022-05-31 15:53 ` DJ Delorie [this message]
2022-05-31 16:47 ` dancol
2022-05-31 16:55 ` Kaz Kylheku
2022-05-31 18:59 ` Anthony Green
2022-05-31 23:16 ` DJ Delorie
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=xn1qw9snp6.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=green@moxielogic.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).