From: Chung-Lin Tang <cltang@codesourcery.com>
To: <libffi-discuss@sourceware.org>
Cc: <green@moxielogic.com>, <ktinker@workforcesoftware.com>
Subject: [PATCH] Workaround ARM VFP issue
Date: Tue, 06 Mar 2012 09:55:00 -0000 [thread overview]
Message-ID: <4F55DF1B.50008@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
This is patch to workaround the issue mentioned in this thread:
http://sourceware.org/ml/libffi-discuss/2012/msg00038.html
The issue is not really that soft-float is broken, but rather the
toolchain used is simply too old, not really because it is old-ABI, but
too old a version of binutils; the .fpu directive, nor VFP instructions
are supported in the assembler, hence even building of the VFP
call/closure shims fail.
This patch is sort of a least attempt to shield away the VFP stuff when
__ARM_EABI__ is not defined. I apologize for such a token workaround, as
it can probably be optimized a bit more, but I just feel it's not
worthwhile; even GCC (recent versions) assumes such assembler features.
Kyle, can you please see if the patch can work for you? If in case it
doesn't, I might also suggest that you try to rebuild your toolchain
with a newer binutils version (at least post circa 2005), which should
at least not fail to build the library.
Thanks,
Chung-Lin
2012-03-06 Chung-Lin Tang <cltang@codesourcery.com>
* src/arm/ffi.c (ffi_call): Add __ARM_EABI__ guard around call
to ffi_call_VFP().
(ffi_prep_closure_loc): Add __ARM_EABI__ guard around use of
ffi_closure_VFP.
* src/arm/sysv.S: Add __ARM_EABI__ guard around VFP code.
[-- Attachment #2.1: Type: application/applefile, Size: 430 bytes --]
[-- Attachment #2.2: ffi.diff --]
[-- Type: application/octet-stream, Size: 1311 bytes --]
diff --git a/src/arm/ffi.c b/src/arm/ffi.c
index 1f8597d..3ccceb9 100644
--- a/src/arm/ffi.c
+++ b/src/arm/ffi.c
@@ -251,8 +251,10 @@ void ffi_call(ffi_cif *cif, void (*fn)(void), void *rvalue, void **avalue)
break;
case FFI_VFP:
+#ifdef __ARM_EABI__
ffi_call_VFP (fn, &ecif, cif->bytes, cif->flags, ecif.rvalue);
break;
+#endif
default:
FFI_ASSERT(0);
@@ -609,8 +611,10 @@ ffi_prep_closure_loc (ffi_closure* closure,
if (cif->abi == FFI_SYSV)
closure_func = &ffi_closure_SYSV;
+#ifdef __ARM_EABI__
else if (cif->abi == FFI_VFP)
closure_func = &ffi_closure_VFP;
+#endif
else
return FFI_BAD_ABI;
diff --git a/src/arm/sysv.S b/src/arm/sysv.S
index 60e2ae3..2505305 100644
--- a/src/arm/sysv.S
+++ b/src/arm/sysv.S
@@ -334,7 +334,8 @@ ARM_FUNC_START ffi_closure_SYSV
/* Below are VFP hard-float ABI call and closure implementations.
- Add VFP FPU directive here. */
+ Add VFP FPU directive here. This is only compiled into the library under EABI. */
+#ifdef __ARM_EABI__
.fpu vfp
@ r0: fn
@@ -491,6 +492,7 @@ ARM_FUNC_START ffi_closure_VFP
.ffi_closure_VFP_end:
UNWIND .fnend
.size CNAME(ffi_closure_VFP),.ffi_closure_VFP_end-CNAME(ffi_closure_VFP)
+#endif
ENTRY(ffi_arm_trampoline)
stmfd sp!, {r0-r3}
next reply other threads:[~2012-03-06 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 9:55 Chung-Lin Tang [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-06 12:38 Chung-Lin Tang
2012-03-06 14:20 ` Kyle Tinker
2012-06-08 21:20 ` Kyle Tinker
2012-03-06 9:58 Chung-Lin Tang
2012-03-06 9:54 Chung-Lin Tang
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=4F55DF1B.50008@codesourcery.com \
--to=cltang@codesourcery.com \
--cc=green@moxielogic.com \
--cc=ktinker@workforcesoftware.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).