patch with larger errors for "float"
paul zimmermann
Paul.Zimmermann@inria.fr
Wed Jan 22 10:08:00 GMT 2020
Dear Carlos,
> >> Just to confirm, does it pass make check without regression?
> >
> > well, not really. I get *before* and after my patch:
> >
> > Summary of test results:
> > 141 FAIL
>
> This is very bad. What are these failures?
I get for example:
FAIL: debug/tst-backtrace2
FAIL: debug/tst-backtrace3
FAIL: debug/tst-backtrace4
FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
FAIL: dlfcn/bug-atexit3
...
FAIL: stdlib/tst-thread-quick_exit
Is there a file where all failures are written?
> Could you please also review Joseph's comment to add the ULPs
> to libm-test-ulps for all 10 functions?
>
> If you have actually found 10 functions with specific inputs
> that have higher error bounds we should expect to see those
> larger error bounds reflected in the libm-test-ulps file.
>
> As it stands it looks like either only 6 functions have larger
> error bounds, or as Joseph says there is a difference between
> how mpcheck and glibc compute ULPs.
as I said, I didn't use the testrun.sh wrapper, thus I was using
glibc 2.29 instead of the development version, which should explain
why some errors were larger. I'll use the development version in
further runs.
Best regards,
Paul
More information about the Libc-alpha
mailing list