aboutsummaryrefslogtreecommitdiff
path: root/benchtests
AgeCommit message (Collapse)Author
2013-04-24Mention files in which fast/slow paths of math functions are implementedSiddhesh Poyarekar
2013-04-23PowerPC: modf optimizationAdhemerval Zanella
This patch implements modf/modff optimization for POWER by focus on FP operations instead of relying in integer ones.
2013-04-17Add benchmark inputs for cos and tanSiddhesh Poyarekar
2013-04-16Define NOT_IN_libc when compiling benchmark programsSiddhesh Poyarekar
2013-04-16Add target bench-cleanSiddhesh Poyarekar
2013-04-15Write to bench.out-tmp only onceSiddhesh Poyarekar
Appending benchmark program output on every run could result in a case where the benchmark run was cancelled, resulting in a partially written file. This file gets used again on the next run, resulting in results being appended to old results. It could have been possible to remove the file before every benchmark run, but it is easier to just write the output to bench.out-tmp only once.
2013-04-15Rebuild benchmark sources when Makefile is updatedSiddhesh Poyarekar
Benchmark programs are generated using parameters from the Makefile, so it is necessary to rebuild them whenever the parameters in the Makefile are updated. Hence, added a dependency for the generated C source on the Makefile so that it gets regenerated when the Makefile is updated.
2013-04-12Move bench target to benchtestsSiddhesh Poyarekar
The bench target will only be used within the benchtests directory.
2013-04-03Add benchmark inputs for atanSiddhesh Poyarekar
Add separate inputs for slow and fast paths of atan
2013-04-02Add benchmark inputs for sinSiddhesh Poyarekar
2013-04-02Add benchmark tests for slowpow and slowexpSiddhesh Poyarekar
Separate benchmarks for the fast and slow implementations of pow and exp since measuring both together doesn't make sense. Adjust the iterations for pow and exp accordingly so that they run long enough for the measurements to be meaningful.
2013-04-01PowerPC: remove branch prediction from rint implementationAdhemerval Zanella
The branch prediction hints is actually hurts performance in this case. The assembly implementation make two assumptions: 1. 'fabs (x) < 2^52' is unlikely and 2. 'x > 0.0' is unlike (if 1. is true). Since it a general floating point function, expected input is not bounded and then it is better to let the hardware handle the branches.
2013-03-15Framework for performance benchmarking of functionsSiddhesh Poyarekar
See benchtests/Makefile to know how to use it.