public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: "Damien Thébault" <damien@dtbo.net>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: Floating-point variadic function call
Date: Mon, 10 Oct 2016 07:17:00 -0000	[thread overview]
Message-ID: <CA+=Sn1mm1s45mQ3f0MVvXMhjn4hyRrSqW6wZzAwGW-+2XkonWw@mail.gmail.com> (raw)
In-Reply-To: <20161010070352.GA11072@han>

On Mon, Oct 10, 2016 at 12:03 AM, Damien Thébault <damien@dtbo.net> wrote:
> Hello,
>
> I am trying to use libffi to call various functions, and my first try
> was with printf(). As this is a variadic function, I used
> ffi_prep_cif_var(). Everything seems to be working, except with floats,
> which are not working, and are even generating wrong memory accesses
> (detected by valgrind).
>
> A similar function with ffi_prep_cif() and floats is working properly.
>
> Could type promotion from float to double be the issue here ?
> Does libffi handle type promotion in variadic calls or is it the
> caller's job ?
>
> I tested on a x86_64 computer both 64-bit and 32-bit versions (the
> latter compiled with -m32) as well as ARM under qemu.
> In all those cases, I didn't get the proper result with floats while
> doubles are ok, as well as chars.

That is because the variadic function ABI is different from the normal
argument ABI on ARM hard-float EABI.  Basically for variadic functions
float are passed via the integer registers while for normal functions,
they are passed via the vfp registers.

Basically you need to use variadic function support in libff.  Use
ffi_prep_cif_var instead of ffi_prep_cif and then don't do:

    for(i=1 ; i<10 ; i++)
    {
        arg_types[i] = &ffi_type_float;
    }


Thanks,
Andrew Pinski

> I've attached a sample source file that reproduces the problem and here
> is the output of one test run:
>
>  $ gcc $(pkg-config --cflags --libs libffi) -std=c99 -pedantic -Wall -Wextra libffi_variadic_printf.c -o libffi_variadic_printf
>  $ ./libffi_variadic_printf
> Non-variadic call:
> [1.100000,2.200000,3.300000,4.400000,5.500000,6.600000,7.700000,8.800000,9.900000]
> result is 83
> Variadic call:
> [0.000000,0.000000,0.000000,0.000000,0.000000,91750.390826,0.000000,0.000000,0.000000]
> result is 87
>
> Thanks,

  reply	other threads:[~2016-10-10  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10  7:04 Damien Thébault
2016-10-10  7:17 ` Andrew Pinski [this message]
2016-10-10  7:27   ` Damien Thébault
2016-10-11 13:27     ` Richard Henderson
2016-10-11 19:12       ` Damien Thébault

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='CA+=Sn1mm1s45mQ3f0MVvXMhjn4hyRrSqW6wZzAwGW-+2XkonWw@mail.gmail.com' \
    --to=pinskia@gcc.gnu.org \
    --cc=damien@dtbo.net \
    --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).