public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Kyle Tinker <ktinker@workforcesoftware.com>
To: Chung-Lin Tang <cltang@codesourcery.com>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>,
	"green@moxielogic.com" <green@moxielogic.com>
Subject: Re: [PATCH] Workaround ARM VFP issue
Date: Fri, 08 Jun 2012 21:20:00 -0000	[thread overview]
Message-ID: <4FD26CA5.70900@workforcesoftware.com> (raw)
In-Reply-To: <4F560526.6070208@codesourcery.com>

Chung-Lin:

First, sorry for the large (3 month) delay.

I've applied the patch and gotten it to compile on our system!  THANK YOU!

We had to define the __SOFTFP__ cflag to get it to compile correctly, 
but the patch worked great once we did that.

Sorry our toolchain is so old...  performance is always a consideration, 
but we shouldn't be making THAT many libffi calls for the changes you 
made to matter.  I certainly wouldn't optimize your code for the sake of 
a toolchain that predates 2005.

Thanks,
*Kyle Tinker* *|* *Software Development Manager* *|* *WorkForce Software*

WorkForce Software — Mitigating Complexity — Ensuring Compliance
— Enabling Strategic HR


From: Chung-Lin Tang <cltang@codesourcery.com>
Sent: Tue, Mar 06, 2012 7:37 AM
To: libffi-discuss@sourceware.org <libffi-discuss@sourceware.org>
CC: "green@moxielogic.com" <green@moxielogic.com>, Kyle Tinker 
<ktinker@workforcesoftware.com>
Subject: [PATCH] Workaround ARM VFP issue


> 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.

  parent reply	other threads:[~2012-06-08 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 12:38 Chung-Lin Tang
2012-03-06 14:20 ` Kyle Tinker
2012-06-08 21:20 ` Kyle Tinker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-06  9:58 Chung-Lin Tang
2012-03-06  9:55 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=4FD26CA5.70900@workforcesoftware.com \
    --to=ktinker@workforcesoftware.com \
    --cc=cltang@codesourcery.com \
    --cc=green@moxielogic.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).