> Mosher's code isn't always-correct; it even given an
error bound in the
> source.
You means this?
/* Multiply by 10**nexp. If precision is 64 bits,
* the maximum relative error incurred in forming 10**n
* for 0 <= n <= 324 is 8.2e-20, at 10**180.
* For 0 <= n <= 999, the peak relative error is
1.4e-19 at 10**947.
* For 0 >= n >= -999, it is -1.55e-19 at 10**-435.
*/
I did try 10e180, 10e947, and 10e-435 -- for those three
acfloat3
does match what his ieee.c spits out.
> Simply using GMP/MPFR would probably be the easiest,
except possibly for
> the autoconf-challenged platforms.
So far NASM has had the nice property of being standalone.
The
trend towards more and more dependencies worries me a little
--
the more complex, the more easily things tend to break.
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nasm-devel mailing list
Nasm-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nasm-devel
a>
|