[OE-core] libm accuracy, eglibc compared to glibc

[Mats Kärrman]

On Wednesday, March 12, 2014 6:37 PM, Phil Blundell wrote:
> On Wed, 2014-03-12 at 15:30 +0000, Mats Kärrman wrote:
>> Does anyone know if this is a known "feature" of eglibc or know any other reason
>> for this difference?
>
> Does eglibc's own libm testsuite pass on your platform?  I wonder if
> oe-core is accidentally building eglibc without "big" libm for you, or
> something like that.  Might be worth checking your option-groups.config
> to make sure.

I have no NFS set up so I have not managed to run the eglibc target tests yet.

I ran the test program I mentioned before on an i.MX6 (arm cortexa9-hf) system
built on Poky/Dora (the PowerPC system is bare-bone OE-core/Dora) and got the
correct results there (i.e identical to my PC et.c.).

Comparing:
.../eglibc/2.18-r0/build-powerpc-oe-linux/option-groups.config (my failing system)
.../eglibc/2.18-r0/build-arm-poky-linux-gnueabi/option-groups.config (arm i.MX6)

They are both identical and both have all options set "= Y".

My "home made" hard float tune for PowerPC looks like this:

------------------------------------------------------------------
# Tune for the e300c3 core
require conf/machine/include/tune-ppce300c3.inc

# Use hardware floating point
AVAILTUNES += "ppce300c3hf"
TUNE_FEATURES_tune-ppce300c3hf = "m32 fpu-hard ppce300c3"
TUNE_PKGARCH_tune-ppce300c3hf = "ppce300c3hf"
PACKAGE_EXTRA_ARCHS_tune-ppce300c3hf = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppce300c3hf"
DEFAULTTUNE = "ppce300c3hf"
------------------------------------------------------------------

Your comments are welcome.

BR // Mats