From: Andreas Tobler <andreast-list@fgznet.ch>
To: Alan Modra <amodra@gmail.com>, libffi-discuss@sourceware.org
Subject: Re: Reinstate powerpc bounce buffer copying in ffi.c
Date: Wed, 13 Nov 2013 19:02:00 -0000 [thread overview]
Message-ID: <5283CCC9.9070508@fgznet.ch> (raw)
In-Reply-To: <20131113140859.GZ20756@bubble.grove.modra.org>
Hi Alan,
On 13.11.13 15:08, Alan Modra wrote:
> Andreas' 2013-02-08 change reverted some breakage for struct return
> values from 2011-11-12, but in so doing reintroduced string
> instructions to sysv.S that are not supported on all powerpc variants.
> This patch properly copies the bounce buffer to destination in C code
> rather than in asm.
>
Thank you!
I can confirm a native powerpc-unknown-freebsd11.0 gives the following:
=== libffi Summary ===
# of expected passes 1819
# of unsupported tests 55
Andreas
> I have tested this on powerpc64-linux, powerpc-linux and
> powerpc-freebsd. Well, the last on powerpc-linux by lying to
> configure with
>
> CC="gcc -m32 -msvr4-struct-return -mlong-double-64" \
> CXX="g++ -m32 -msvr4-struct-return -mlong-double-64" \
> /src/libffi-current/configure --build=powerpc-freebsd
>
> and then
>
> make && make CC="gcc -m32" CXX="g++ -m32" \
> RUNTESTFLAGS=--target_board=unix/-m32/-msvr4-struct-return/-mlong-double-64\
> check
>
> * src/powerpc/ffi.c (ffi_prep_cif_machdep): Revert 2013-02-08
> change. Do not consume an int arg when returning a small struct
> for FFI_SYSV ABI.
> (ffi_call): Only use bounce buffer when FLAG_RETURNS_SMST.
> Properly copy bounce buffer to destination.
> * src/powerpc/sysv.S: Revert 2013-02-08 change.
> * src/powerpc/ppc_closure.S: Remove stray '+'.
prev parent reply other threads:[~2013-11-13 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 14:09 Alan Modra
2013-11-13 19:02 ` Andreas Tobler [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=5283CCC9.9070508@fgznet.ch \
--to=andreast-list@fgznet.ch \
--cc=amodra@gmail.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).