<feed xmlns='http://www.w3.org/2005/Atom'>
<title>glibc/benchtests/fmaxf-inputs, branch master</title>
<subtitle>Fork of glibc for development</subtitle>
<id>https://git.zx2c4.com/glibc/atom/benchtests/fmaxf-inputs?h=master</id>
<link rel='self' href='https://git.zx2c4.com/glibc/atom/benchtests/fmaxf-inputs?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/'/>
<updated>2016-12-19T18:04:16Z</updated>
<entry>
<title>benchtests: Add fmaxf/fminf benchmarks</title>
<updated>2016-12-19T18:04:16Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2016-12-19T13:00:45Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=da16c9b524908fe0353efc4af8eab6a5ad5ea50b'/>
<id>urn:sha1:da16c9b524908fe0353efc4af8eab6a5ad5ea50b</id>
<content type='text'>
This patch adds fmaxf and fminf benchtests.  It is based on
math/s_fmax_template.c implementation which checks for basically four
different classes:

  1. if x is greater or equal than y.
  2. if x is less than y.
  3. if x or y is signaling.
  4. if y is nan.

Cases 1 and 2 are used for default input number (by mixing normal double
numbers and infinity), while case 3 and 4 are used each for on for a
benchmark class.

Checked on x86_64-linux-gnu and powerpc64-linux-gnu.

	* benchtests/Makefile (bench-math): Add fminf and fmaxf.
	(CFLAGS-bench-fmaxf.c): New rule.
	(CFLAGS-bench-fminf.c): Likewise.
        * benchtests/fmaxf-inputs: New file.
        * benchtests/fminf-inputs: Likewise.
</content>
</entry>
</feed>
