public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libffi/60073] [4.9 regression] 64-bit libffi.call/cls_double_va.c FAILs after recent modification Date: Wed, 05 Feb 2014 22:57:00 -0000 [thread overview] Message-ID: <bug-60073-4-VFURCcpX2d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60073-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60073 --- Comment #7 from Alan Modra <amodra at gmail dot com> --- The variadic support in libfii is fairly recent. And yes, it might have been there earlier if the testcases actually tested what they were suppose to test! Note that powerpc64-gcc passes fp arguments corresponding to the ellipsis part of variadic functions in both the parameter save area and fp registers, contrary to the ABI which says they just go in the parameter save area if the function has a prototype. I think this was in part to satisfy libffi, where without variadic support you don't know whether a function call is normal or variadic and thus the powerpc libffi support had to pull fp values from fp registers. So we broke gcc (a little) to satisfy libffi..
next prev parent reply other threads:[~2014-02-05 22:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-05 12:33 [Bug libffi/60073] New: [4.9 regression] 64-bit libffi.call/cls_double_va.c FAILs on Solaris/SPARC ro at gcc dot gnu.org 2014-02-05 12:34 ` [Bug libffi/60073] " ro at gcc dot gnu.org 2014-02-05 13:04 ` ebotcazou at gcc dot gnu.org 2014-02-05 13:39 ` amodra at gmail dot com 2014-02-05 16:29 ` [Bug libffi/60073] [4.9 regression] 64-bit libffi.call/cls_double_va.c FAILs after recent modification ebotcazou at gcc dot gnu.org 2014-02-05 16:30 ` ebotcazou at gcc dot gnu.org 2014-02-05 18:17 ` ebotcazou at gcc dot gnu.org 2014-02-05 21:08 ` ebotcazou at gcc dot gnu.org 2014-02-05 22:57 ` amodra at gmail dot com [this message] 2014-02-13 16:18 ` ebotcazou at gcc dot gnu.org 2014-02-13 16:19 ` ebotcazou at gcc dot gnu.org 2014-02-17 12:00 ` ebotcazou at gcc dot gnu.org
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=bug-60073-4-VFURCcpX2d@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).