diff options
Diffstat (limited to 'math/README.libm-test')
| -rw-r--r-- | math/README.libm-test | 33 |
1 files changed, 13 insertions, 20 deletions
diff --git a/math/README.libm-test b/math/README.libm-test index 53172bbff8..28d7a2ed28 100644 --- a/math/README.libm-test +++ b/math/README.libm-test @@ -35,18 +35,14 @@ deviate from the expected results and still be considered correct. The test drivers "test-double-<func>.c", "test-float-<func>.c", and "test-ldouble-<func>.c", generated by the Makefile, test the normal -double, float and long double implementation of libm. The test -drivers with an 'i' in their name ("test-idouble-<func>.c", -"test-ifloat-<func>.c", and "test-ildoubl-<func>.c") test the -corresponding inline functions (where available - otherwise they also -test the real functions in libm). Each driver selects the desired -real floating type to exercise the math functions to test with (float, -double, or long double) by defining a small set of macros just before -including the generic "libm-test.c" file. Each driver also either -defines or undefines the __NO_MATH_INLINES macro just before including -"libm-test-<func>.c" to select either the real or inline functions, -respectively. Each driver is compiled into a single executable test -program with the corresponding name. +double, float and long double implementation of libm. Each driver +selects the desired real floating type to exercise the math functions +to test with (float, double, or long double) by defining a small set +of macros just before including the generic "libm-test.c" file. Each +driver also either defines or undefines the __NO_MATH_INLINES macro +just before including "libm-test-<func>.c" to select either the real +or inline functions, respectively. Each driver is compiled into a +single executable test program with the corresponding name. As mentioned above, the "gen-libm-test.py" script looks for a file named "libm-test-ulps" in the platform specific sysdep directory (or @@ -100,10 +96,9 @@ Since libm-test-ulps can be generated automatically, just a few notes. The file contains lines for maximal errors of single functions, like: Function "yn": -idouble: 6 +double: 6 -The keywords are float, ifloat, double, idouble, ldouble and ildouble -(the prefix i stands for inline). +The keywords are float, double, and ldouble. Adding tests to libm-test-<func>.inc ==================================== @@ -143,11 +138,9 @@ How to read the test output Running each test on its own at the default level of verbosity will print on stdout a line describing the implementation of math functions -exercised by the test (float, double, or long double), along with -whether the inline set has been selected, regardless of whether or -not any inline functions actually exist. This is then followed by -the details of test failures (if any). The output concludes by -a summary listing the number of test cases exercised and the number +exercised by the test (float, double, or long double). This is then +followed by the details of test failures (if any). The output concludes +by a summary listing the number of test cases exercised and the number of test failures uncovered. For each test failure (and for each test case at higher levels of |