summaryrefslogtreecommitdiff
path: root/floattest.c
Commit message (Collapse)AuthorAgeFilesLines
* repository beautification, part 2:Chris Kuethe2009-03-021-256/+0
| | | | rename the test programs to test_$(subsystem).c
* better.Chris Kuethe2007-12-091-6/+8
|
* run all the tests, even if one fails.Chris Kuethe2007-12-091-53/+92
| | | | | it might be fun to know just how broken your floating point is ... (i'm looking at a certain popular virtualization environment here)
* Floating point math test integrated into configure. Chris Kuethe2006-11-101-2/+5
| | | | | It is not (yet) a fatal error if floattest fails, but you will be warned, and told which test fails to run.
* Somewhat more involved floating point exerciser. Chris Kuethe2006-11-101-26/+182
| | | | | | | | | | | Testing equality of floating point numbers (f == g or f != g) is usually Considered Harmful because floats and doubles are only approximations. Granted, some numbers can be represented precisely - which is what I use in this test suite. All intermediate results can be precisely represented as well. The same tests are used for both single and double precision numbers. Tested on i386, amd64 and sparc64. ARM tests to follow shortly.
* Bounded string functions.Chris Kuethe2006-11-101-2/+2
|
* Modify floattest.c slightly so it returns 1 if the test fails.Eric S. Raymond2006-11-101-9/+14
|
* Eliminate a compiler warning. And I got the -o/-O flags in the wrong order.Chris Kuethe2006-11-101-2/+2
|
* This is floattest...Chris Kuethe2006-11-101-0/+51
...a simple utility to check that your toolchain can do single and double precision math properly. I've heard trouble reports from two embedded user where the problem was traced to a buggy toolchain.