From: Andrew Haley <aph@redhat.com>
To: libffi-discuss@sourceware.org
Subject: Re: Also: problem with return value in ffi_call on PPC64.
Date: Tue, 30 May 2017 08:27:00 -0000 [thread overview]
Message-ID: <2cca1ce1-3ccb-843a-347e-bd2eaa60ca97@redhat.com> (raw)
In-Reply-To: <a1bda55849470c990b5c319c92351cf7@mail.kylheku.com>
On 28/05/17 02:36, Kaz Kylheku (libffi) wrote:
> Are users supposed to assume that the return value has been widened to a
> register-wide (8 byte) value regardless of its declared FFI type?
Yes.
> Why doesn't that convention apply to the arguments, then? When dup is
> being called above, the int value is being written at the bottom of the
> argument buffer, not displaced by four bytes.
It's more of a historical accident than anything planned. But it's not
important enough to break backwards compatibility.
--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
next prev parent reply other threads:[~2017-05-30 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 1:36 Kaz Kylheku (libffi)
2017-05-30 8:27 ` Andrew Haley [this message]
2017-05-28 2:16 Kaz Kylheku (libffi)
2017-05-28 18:23 ` Sergei Trofimovich via libffi-discuss
2017-05-30 1:24 ` 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=2cca1ce1-3ccb-843a-347e-bd2eaa60ca97@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).