You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the new binarybuilder build from #26, we now have the ability to test on 32 bit systems.
This led to finding the test failure noted in JuliaIntervals/IntervalArithmetic.jl#440. These have probably always existed with this package on 32 bit linux, but nobody noticed until now.
I've built crlibm locally with 32 bit gcc (from a 64 bit host) and have managed to reproduce the failures using the underlying crlibm test suite. Build instructions:
# Get the source from https://github.com/taschini/crlibm
# Build
./prepare
./configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu CC=i686-linux-gnu-gcc
make
make check
This results in many test failures (log summary attached at bottom)
I also build crlibm in a 32 bit userland inside a docker container with the default prepare and configure and all build settings autodetected — I found that the errors persist. So these may be real bugs in crlibm (or its build system) rather than an issue with cross compilation.
It seems that CRLibm.jl should not use the current binarybuilder build for 32 bit systems unless this is fixed. The simple fix is to fall back to MPFR on 32 bit.
On a related note, it would be nice to convert the relatively comprehensive tests which come with CRLibm itself into tests for this package. They are well designed data-driven tests so the test files could just be copied into this package and run with a new test runner.
With the new binarybuilder build from #26, we now have the ability to test on 32 bit systems.
This led to finding the test failure noted in JuliaIntervals/IntervalArithmetic.jl#440. These have probably always existed with this package on 32 bit linux, but nobody noticed until now.
I've built crlibm locally with 32 bit gcc (from a 64 bit host) and have managed to reproduce the failures using the underlying crlibm test suite. Build instructions:
This results in many test failures (log summary attached at bottom)
I also build crlibm in a 32 bit userland inside a docker container with the default
prepare
andconfigure
and all build settings autodetected — I found that the errors persist. So these may be real bugs in crlibm (or its build system) rather than an issue with cross compilation.It seems that CRLibm.jl should not use the current binarybuilder build for 32 bit systems unless this is fixed. The simple fix is to fall back to MPFR on 32 bit.
On a related note, it would be nice to convert the relatively comprehensive tests which come with CRLibm itself into tests for this package. They are well designed data-driven tests so the test files could just be copied into this package and run with a new test runner.
Test failure log summary:
The text was updated successfully, but these errors were encountered: