ARM neon pseudo op
mohr at linuxcertified.com
Tue Apr 2 19:42:34 CEST 2013
If your eventual target is a "fat" binary, using "-mfpu=neon" in CFLAGS
is a bad idea (at least for Android). It would be far better to
approach the problem as Niels did, using ".fpu neon" as required. That
way, non-neon code can be selected at runtime if necessary for the
critical code paths. Certain ARM phones will have ARMv5, others ARMv7,
and yet others ARMv7 with neon. This information isn't available until
runtime for an APK distributed on the Android Market.
On 04/02/2013 02:58 AM, Niels Möller wrote:
> Torbjorn Granlund <tg at gmplib.org> writes:
>> I need the first few dozen lines from the configure output to have a
>> guess about what might go wrong. You might actually compare the output
>> to that of panda.gmplib.org yourself.
> Hmm, it's supposed to be a flag (-mfpu=neon) on the gcc command line?
> Then it's my fault... I had set CFLAGS manually to what gmp's configure
> selected for me some month or two ago, plus a "-g".
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4272 bytes
Desc: S/MIME Cryptographic Signature
More information about the gmp-devel