aboutsummaryrefslogtreecommitdiff
path: root/doc/testfloat_gen.html
diff options
context:
space:
mode:
authorJohn Hauser <jhauser@eecs.berkeley.edu>2016-07-22 18:04:32 -0700
committerJohn Hauser <jhauser@eecs.berkeley.edu>2016-07-22 18:04:32 -0700
commitddfb9e70c434ae238635784ce66cb7ed93d0a2e7 (patch)
tree3502b5d96dcdbc5ad0c16c00caf4cd21428314b3 /doc/testfloat_gen.html
parent11a6a656c7651695deacfdcda9c5d80fdbc05fee (diff)
downloadberkeley-testfloat-3-ddfb9e70c434ae238635784ce66cb7ed93d0a2e7.zip
berkeley-testfloat-3-ddfb9e70c434ae238635784ce66cb7ed93d0a2e7.tar.gz
berkeley-testfloat-3-ddfb9e70c434ae238635784ce66cb7ed93d0a2e7.tar.bz2
Release 3b. See "doc/TestFloat-history.html".
Diffstat (limited to 'doc/testfloat_gen.html')
-rw-r--r--doc/testfloat_gen.html27
1 files changed, 22 insertions, 5 deletions
diff --git a/doc/testfloat_gen.html b/doc/testfloat_gen.html
index 9e24c54..306e3c5 100644
--- a/doc/testfloat_gen.html
+++ b/doc/testfloat_gen.html
@@ -7,11 +7,11 @@
<BODY>
-<H1>Berkeley TestFloat Release 3a: <CODE>testfloat_gen</CODE></H1>
+<H1>Berkeley TestFloat Release 3b: <CODE>testfloat_gen</CODE></H1>
<P>
John R. Hauser<BR>
-2015 October 23<BR>
+2016 July 22<BR>
</P>
@@ -89,6 +89,10 @@ A <CODE>&lt;type&gt;</CODE> can be one of the following:
<TD>signed <NOBR>64-bit</NOBR> integers</TD>
</TR>
<TR>
+<TD><CODE>f16 [&lt;num&gt;]</CODE></TD>
+<TD>one or more <NOBR>16-bit</NOBR> half-precision floating-point values</TD>
+</TR>
+<TR>
<TD><CODE>f32 [&lt;num&gt;]</CODE></TD>
<TD>one or more <NOBR>32-bit</NOBR> single-precision floating-point values</TD>
</TR>
@@ -130,7 +134,7 @@ output from <CODE>testfloat_gen</CODE> contains not only the operands for that
operation (as would be generated by an appropriate <CODE>&lt;type&gt;</CODE>
argument) but also the expected results as determined by
<CODE>testfloat_gen</CODE>&rsquo;s internal floating-point emulation
-(SoftFloat).
+(Berkeley SoftFloat).
The available operation names are listed in
<A HREF="TestFloat-general.html"><NOBR><CODE>TestFloat-general.html</CODE></NOBR></A>.
In all cases, floating-point operations have two results:
@@ -170,6 +174,19 @@ This can be used, for example, to indicate to a downstream program what kind of
test to perform for the test cases that follow.
</P>
+<H3><CODE>-seed &lt;num&gt;</CODE></H3>
+
+<P>
+The <CODE>-seed</CODE> option sets the seed for the pseudo-random number
+generator used for generating test cases.
+The argument to <CODE>-seed</CODE> is a nonnegative integer.
+Executing the same <CODE>testfloat_gen</CODE> program with the same arguments
+(including the same pseudo-random number seed) should always generate the same
+sequence of test cases, whereas changing the pseudo-random number seed should
+result in a different sequence of test cases.
+The default seed number <NOBR>is 1</NOBR>.
+</P>
+
<H3><CODE>-level &lt;num&gt;</CODE></H3>
<P>
@@ -245,8 +262,8 @@ be detected before rounding, while <CODE>-tininessafter</CODE> indicates that
tininess on underflow will be detected after rounding.
These options are ignored for operations that are exact and thus do not round.
When the method of tininess detection matters but is not specified, the default
-is to detect tininess on underflow before rounding, same as
-<CODE>-tininessbefore</CODE>.
+is to detect tininess on underflow after rounding, same as
+<CODE>-tininessafter</CODE>.
</P>
<H3><CODE>-notexact, -exact</CODE></H3>