From: Richard Henderson <rth@redhat.com>
To: "Stéphane Glondu" <steph@glondu.net>, libffi-discuss@sourceware.org
Subject: Re: Function returning uint16
Date: Thu, 16 Jun 2016 19:15:00 -0000 [thread overview]
Message-ID: <862a29c4-6759-44e9-89c0-59270b35d514@redhat.com> (raw)
In-Reply-To: <5762BFD6.1020704@glondu.net>
On 06/16/2016 08:03 AM, Stéphane Glondu wrote:
> Hello,
>
> I am trying to debug
>
> https://github.com/ocamllabs/ocaml-ctypes/issues/404
>
> and I realized that the following code (on amd64):
>
> #include <stdio.h>
> #include <stdint.h>
> #include <ffi.h>
>
> uint16_t retrieve() {
> return 0x4242;
> }
>
> int main() {
> uint16_t r[2] = { 0xdead, 0xbeef };
> ffi_cif cif;
> printf("r = {%x, %x}\n", r[0], r[1]);
> ffi_prep_cif(&cif, FFI_DEFAULT_ABI, 0, &ffi_type_uint16, NULL);
> ffi_call(&cif, FFI_FN(retrieve), &r[0], NULL);
> printf("r = {%x, %x}\n", r[0], r[1]);
> return 0;
> }
>
> returns:
>
> r = {dead, beef}
> r = {4242, 0}
>
> Is that expected? I don't expect r[1] to be overwritten...
It is expected. In the documentation,
In most situations, @samp{libffi} will handle promotion according to
the ABI. However, for historical reasons, there is a special case
with return values that must be handled by your code. In particular,
for integral (not @code{struct}) types that are narrower than the
system register size, the return value will be widened by
@samp{libffi}. @samp{libffi} provides a type, @code{ffi_arg}, that
can be used as the return type. For example, if the CIF was defined
with a return type of @code{char}, @samp{libffi} will try to store a
full @code{ffi_arg} into the return value.
r~
prev parent reply other threads:[~2016-06-16 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 15:04 Stéphane Glondu
2016-06-16 19:15 ` Richard Henderson [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=862a29c4-6759-44e9-89c0-59270b35d514@redhat.com \
--to=rth@redhat.com \
--cc=libffi-discuss@sourceware.org \
--cc=steph@glondu.net \
/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).