glibc/benchtests/sin-inputs

0.9
2.3
3.7
3.9
4.0
4.7
5.9
# sin slowest path at 768 bits
# Implemented in sysdeps/ieee754/dbl-64/sincos32.c
## name: 768bits
0.93340582292648832662962377071381
2.3328432680770916363144351635128
3.7439477503636453548097051680088
3.9225160069792437411706487182528
4.0711651639931289992091478779912
4.7858438478542097982426639646292
5.9840767662578002727968851104379
Add benchmark inputs for sin 2013-04-01 09:15:54 +00:00			`0.9`
			`2.3`
			`3.7`
			`3.9`
			`4.0`
			`4.7`
			`5.9`
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 08:47:57 +00:00			`# sin slowest path at 768 bits`
			`# Implemented in sysdeps/ieee754/dbl-64/sincos32.c`
			`## name: 768bits`
			`0.93340582292648832662962377071381`
			`2.3328432680770916363144351635128`
			`3.7439477503636453548097051680088`
			`3.9225160069792437411706487182528`
			`4.0711651639931289992091478779912`
			`4.7858438478542097982426639646292`
			`5.9840767662578002727968851104379`