diff options
author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2006-04-11 13:54:39 +0000 |
---|---|---|
committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2006-04-11 13:54:39 +0000 |
commit | 8cfe8221c00469ca7bcf7093fc9b3796514535c8 (patch) | |
tree | 9071a2f7af31ed6e04094af3e241b94ced986972 /FAQ.html | |
parent | 7466f49a6563f8cab306e0b1dfafed65e87dd6ba (diff) | |
download | mpfr-8cfe8221c00469ca7bcf7093fc9b3796514535c8.tar.gz |
FAQ update.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@4066 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'FAQ.html')
-rw-r--r-- | FAQ.html | 32 |
1 files changed, 21 insertions, 11 deletions
@@ -55,17 +55,27 @@ bugs page.</strong></p> from <cite><acronym>GMP</acronym></cite> and <cite><acronym>MPFR</acronym></cite>?</dt> -<dd>Unlike <cite><acronym>MPF</acronym></cite>, the precision of a -<cite><acronym>MPFR</acronym></cite> variable is the <em>exact</em> -number of bits used for its mantissa. This implies that -<cite><acronym>MPFR</acronym></cite> results do not depend on the -number of bits (16, 32, 64 or more) of the underlying architecture. -Also, <cite><acronym>MPFR</acronym></cite> provides an additional -rounding mode argument to its functions; furthermore, it is guaranteed -that the result of any operation is the nearest possible -floating-point value from the exact result (considering the input -variables as exact values), taking into account the precision of the -destination variable and the rounding mode.</dd> +<dd><p>The main differences are:</p> +<ul> +<li>The precision of a <cite><acronym>MPFR</acronym></cite> variable +is the <em>exact</em> number of bits used for its mantissa, whereas in +<cite><acronym>MPF</acronym></cite>, the precision requested by the user +is a minimum value (<cite><acronym>MPF</acronym></cite> generally uses a +higher precision). With the additional difference below, this implies that +the <cite><acronym>MPFR</acronym></cite> results do not depend on the +number of bits (16, 32, 64 or more) of the underlying architecture.</li> +<li><cite><acronym>MPFR</acronym></cite> provides an additional rounding +mode argument to its functions; furthermore, it is guaranteed that the +result of any operation is the nearest possible floating-point value from +the exact result (considering the input variables as exact values), taking +into account the precision of the destination variable and the rounding +mode. <cite><acronym>MPFR</acronym></cite> also says whether the rounded +result is above or below the exact result.</li> +<li><cite><acronym>MPFR</acronym></cite> supports much more functions +(in particular transcendental functions such as exponentials, logarithms, +trigonometric functions and so on) and special values: signed zeros, +infinities, not-a-number (NaN).</li> +</ul></dd> <dt>How to convert my program written using <cite><acronym>MPF</acronym></cite> to |