Home | History | Annotate | Download | only in libm
History log of /src/tests/lib/libm/t_exp.c
RevisionDateAuthorComments
 1.9  07-Nov-2018  riastradh Fix up libm tests.

- Fix up last few digits of a lot of known-answer tests.

Confirmed with GNU mpfr to 200 bits of precision and cross-checked
with whatever libm Ubuntu ships with.

- Test relative error, not absolute error.

- Set bounds in terms of *_EPSILON, not magic numbers.

*_EPSILON is twice the largest relative error of a correctly
rounded operation, and equal to the largest relative error of an
operation with up to 1ulp error.

Most of the operations we're testing are not correctly rounded, but
they ought to be no more than 1ulp away. For the few cases where
that's not a priori clear (like comparing cbrt and pow(x, 1/3)),
use twice *_EPSILON to allow some leeway.

- Write the success condition positively as error <= eps.

This comes out false if the result is a NaN, meaning failure. In
contrast, if we write error > eps for the _failure_ condition, then
if the result is a NaN, it will also come out false, but meaning
success, which is not what we want.

- Fix the trigonometric test cases near bad spots.

sin(pi - d) for nonzero d is not zero; it is d + O(d^3). pi is not
a floating-point number, so these results should be approximately
the nonzero error of our approximation to pi. Likewise with
cos(pi/2 - d) and tan(pi + d).

(Yes, I know the sin _function_ is ill-conditioned near pi so you
shouldn't pass approximate inputs near there, but that's separate
from whether a sin _implementation_ gives an answer that is wrong
by quintillions of ulps.)

Since on x86 (i386 and amd64 alike) we currently use x87 hardware
trigonometric instructions, which are bad, these are marked xfail
on x86 for now until we switch to software implementations (coming
soon to a repository near you).

- Use %.8g, %.17g, %.35g to print float, double, long double in failures.

This should be enough to identify the problematic outputs and/or
reproduce the computation, even if long double is binary128 with
115 bits of precision.

If there are any new libm test failures after this, tell me what
architecture you're on and send me the atf output and I'll try to
figure it out.
 1.8  07-Oct-2014  gson branches: 1.8.14; 1.8.16;
In the exp2_values test case, provide separate expected return values
for the float case, reflecting the actual exp2f() argument value after
rounding to float precision. Fixes PR lib/49256. Thanks to Makoto
Kamada and Tetsuya Isaki for the analysis.
 1.7  17-Mar-2014  martin branches: 1.7.4;
Handle VAX
 1.6  16-Mar-2014  dsl Add a lot more tests for exp2() and exp2f().
exp2f(7.7) and exp2f(8.8) seem too far from their expected values
(especially the latter).
exp2(-1023) and below are badly broken.
 1.5  03-Mar-2014  martin Remove all cargo-cult #ifndef __vax__ from the tests, that just paper
over bugs in the vax libm.
 1.4  27-Feb-2014  joerg Avoid promotion in subexpressions.
 1.3  09-Apr-2013  isaki Tune the epsilon about each value for exp{,f}_product.
 1.2  30-May-2012  jruoho branches: 1.2.2;
Add patch from Tetsuya Isaki in PR lib/46433.
 1.1  18-Sep-2011  jruoho branches: 1.1.2;
IEEE checks for the exponential family.
 1.1.2.2  22-May-2014  yamt sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs. ("Protocol error: too many arguments")
 1.1.2.1  30-Oct-2012  yamt sync with head
 1.2.2.2  20-Aug-2014  tls Rebase to HEAD as of a few days ago.
 1.2.2.1  23-Jun-2013  tls resync from head
 1.7.4.1  07-Dec-2014  martin Pull up following revision(s) (requested by gson in ticket #296):
tests/lib/libm/t_exp.c: revision 1.8
In the exp2_values test case, provide separate expected return values
for the float case, reflecting the actual exp2f() argument value after
rounding to float precision. Fixes PR lib/49256. Thanks to Makoto
Kamada and Tetsuya Isaki for the analysis.
 1.8.16.1  10-Jun-2019  christos Sync with HEAD
 1.8.14.1  26-Nov-2018  pgoyette Sync with HEAD, resolve a couple of conflicts

RSS XML Feed