glibc/benchtests/tan-inputs

## args: double
## ret: double
## includes: math.h
0x1.dffffffffff1ep-22
# tan slowest path at 768 bits
# Implemented in sysdeps/ieee754/dbl-64/mptan.c
## name: 768bits
0x1.dffffffffff1fp-22
Add more directives to benchmark input files This patch adds some more directives to the benchmark inputs file, moving functionality from the Makefile and making the code generation script a bit cleaner. The function argument and return types that were earlier added as variables in the makefile and passed to the script via command line arguments are now the 'args' and 'ret' directive respectively. 'args' should be a colon separated list of argument types (skipped if the function doesn't accept any arguments) and 'ret' should be the return type. Additionally, an 'includes' directive may have a comma separated list of headers to include in the source. For example, the pow input file now looks like this: 42.0, 42.0 1.0000000000000020, 1.5 I did this to unclutter the benchtests Makefile a bit and eventually eliminate dependency of the tests on the Makefile and have tests depend on their respective include files only. 2013-10-07 08:21:24 +02:00			`## args: double`
			`## ret: double`
			`## includes: math.h`
Add benchmark inputs for cos and tan 2013-04-17 14:15:55 +02:00			`0x1.dffffffffff1ep-22`
Allow multiple input domains to be run in the same benchmark program Some math functions have distinct performance characteristics in specific domains of inputs, where some inputs return via a fast path while other inputs require multiple precision calculations, that too at different precision levels. The way to implement different domains was to have a separate source file and benchmark definition, resulting in separate programs. This clutters up the benchmark, so this change allows these domains to be consolidated into the same input file. To do this, the input file format is now enhanced to allow comments with a preceding # and directives with two # at the begining of a line. A directive that looks like: tells the benchmark generation script that what follows is a different domain of inputs. The value of the 'name' directive (in this case, foo) is used in the output. The two input domains are then executed sequentially and their results collated separately. with the above directive, there would be two lines in the result that look like: func(): .... func(foo): ... 2013-04-30 10:47:57 +02:00			`# tan slowest path at 768 bits`
			`# Implemented in sysdeps/ieee754/dbl-64/mptan.c`
			`## name: 768bits`
			`0x1.dffffffffff1fp-22`