You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

193 lines
9.3 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- This manual describes how to install and use the GNU multiple precision
arithmetic library, version 6.1.0.
Copyright 1991, 1993-2015 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document under
the terms of the GNU Free Documentation License, Version 1.3 or any later
version published by the Free Software Foundation; with no Invariant Sections,
with the Front-Cover Texts being "A GNU Manual", and with the Back-Cover
Texts being "You have freedom to copy and modify this GNU Manual, like GNU
software". A copy of the license is included in
GNU Free Documentation License. -->
<!-- Created by GNU Texinfo 6.4, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Initializing Floats (GNU MP 6.1.0)</title>
<meta name="description" content="How to install and use the GNU multiple precision arithmetic library, version 6.1.0.">
<meta name="keywords" content="Initializing Floats (GNU MP 6.1.0)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link href="index.html#Top" rel="start" title="Top">
<link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
<link href="Floating_002dpoint-Functions.html#Floating_002dpoint-Functions" rel="up" title="Floating-point Functions">
<link href="Assigning-Floats.html#Assigning-Floats" rel="next" title="Assigning Floats">
<link href="Floating_002dpoint-Functions.html#Floating_002dpoint-Functions" rel="prev" title="Floating-point Functions">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="Initializing-Floats"></a>
<div class="header">
<p>
Next: <a href="Assigning-Floats.html#Assigning-Floats" accesskey="n" rel="next">Assigning Floats</a>, Previous: <a href="Floating_002dpoint-Functions.html#Floating_002dpoint-Functions" accesskey="p" rel="prev">Floating-point Functions</a>, Up: <a href="Floating_002dpoint-Functions.html#Floating_002dpoint-Functions" accesskey="u" rel="up">Floating-point Functions</a> &nbsp; [<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Initialization-Functions-1"></a>
<h3 class="section">7.1 Initialization Functions</h3>
<a name="index-Float-initialization-functions"></a>
<a name="index-Initialization-functions-3"></a>
<dl>
<dt><a name="index-mpf_005fset_005fdefault_005fprec"></a>Function: <em>void</em> <strong>mpf_set_default_prec</strong> <em>(mp_bitcnt_t <var>prec</var>)</em></dt>
<dd><p>Set the default precision to be <strong>at least</strong> <var>prec</var> bits. All
subsequent calls to <code>mpf_init</code> will use this precision, but previously
initialized variables are unaffected.
</p></dd></dl>
<dl>
<dt><a name="index-mpf_005fget_005fdefault_005fprec"></a>Function: <em>mp_bitcnt_t</em> <strong>mpf_get_default_prec</strong> <em>(void)</em></dt>
<dd><p>Return the default precision actually used.
</p></dd></dl>
<p>An <code>mpf_t</code> object must be initialized before storing the first value in
it. The functions <code>mpf_init</code> and <code>mpf_init2</code> are used for that
purpose.
</p>
<dl>
<dt><a name="index-mpf_005finit"></a>Function: <em>void</em> <strong>mpf_init</strong> <em>(mpf_t <var>x</var>)</em></dt>
<dd><p>Initialize <var>x</var> to 0. Normally, a variable should be initialized once only
or at least be cleared, using <code>mpf_clear</code>, between initializations. The
precision of <var>x</var> is undefined unless a default precision has already been
established by a call to <code>mpf_set_default_prec</code>.
</p></dd></dl>
<dl>
<dt><a name="index-mpf_005finit2"></a>Function: <em>void</em> <strong>mpf_init2</strong> <em>(mpf_t <var>x</var>, mp_bitcnt_t <var>prec</var>)</em></dt>
<dd><p>Initialize <var>x</var> to 0 and set its precision to be <strong>at least</strong>
<var>prec</var> bits. Normally, a variable should be initialized once only or at
least be cleared, using <code>mpf_clear</code>, between initializations.
</p></dd></dl>
<dl>
<dt><a name="index-mpf_005finits"></a>Function: <em>void</em> <strong>mpf_inits</strong> <em>(mpf_t <var>x</var>, ...)</em></dt>
<dd><p>Initialize a NULL-terminated list of <code>mpf_t</code> variables, and set their
values to 0. The precision of the initialized variables is undefined unless a
default precision has already been established by a call to
<code>mpf_set_default_prec</code>.
</p></dd></dl>
<dl>
<dt><a name="index-mpf_005fclear"></a>Function: <em>void</em> <strong>mpf_clear</strong> <em>(mpf_t <var>x</var>)</em></dt>
<dd><p>Free the space occupied by <var>x</var>. Make sure to call this function for all
<code>mpf_t</code> variables when you are done with them.
</p></dd></dl>
<dl>
<dt><a name="index-mpf_005fclears"></a>Function: <em>void</em> <strong>mpf_clears</strong> <em>(mpf_t <var>x</var>, ...)</em></dt>
<dd><p>Free the space occupied by a NULL-terminated list of <code>mpf_t</code> variables.
</p></dd></dl>
<p>Here is an example on how to initialize floating-point variables:
</p><div class="example">
<pre class="example">{
mpf_t x, y;
mpf_init (x); /* use default precision */
mpf_init2 (y, 256); /* precision <em>at least</em> 256 bits */
&hellip;
/* Unless the program is about to exit, do ... */
mpf_clear (x);
mpf_clear (y);
}
</pre></div>
<p>The following three functions are useful for changing the precision during a
calculation. A typical use would be for adjusting the precision gradually in
iterative algorithms like Newton-Raphson, making the computation precision
closely match the actual accurate part of the numbers.
</p>
<dl>
<dt><a name="index-mpf_005fget_005fprec"></a>Function: <em>mp_bitcnt_t</em> <strong>mpf_get_prec</strong> <em>(const mpf_t <var>op</var>)</em></dt>
<dd><p>Return the current precision of <var>op</var>, in bits.
</p></dd></dl>
<dl>
<dt><a name="index-mpf_005fset_005fprec"></a>Function: <em>void</em> <strong>mpf_set_prec</strong> <em>(mpf_t <var>rop</var>, mp_bitcnt_t <var>prec</var>)</em></dt>
<dd><p>Set the precision of <var>rop</var> to be <strong>at least</strong> <var>prec</var> bits. The
value in <var>rop</var> will be truncated to the new precision.
</p>
<p>This function requires a call to <code>realloc</code>, and so should not be used in
a tight loop.
</p></dd></dl>
<dl>
<dt><a name="index-mpf_005fset_005fprec_005fraw"></a>Function: <em>void</em> <strong>mpf_set_prec_raw</strong> <em>(mpf_t <var>rop</var>, mp_bitcnt_t <var>prec</var>)</em></dt>
<dd><p>Set the precision of <var>rop</var> to be <strong>at least</strong> <var>prec</var> bits,
without changing the memory allocated.
</p>
<p><var>prec</var> must be no more than the allocated precision for <var>rop</var>, that
being the precision when <var>rop</var> was initialized, or in the most recent
<code>mpf_set_prec</code>.
</p>
<p>The value in <var>rop</var> is unchanged, and in particular if it had a higher
precision than <var>prec</var> it will retain that higher precision. New values
written to <var>rop</var> will use the new <var>prec</var>.
</p>
<p>Before calling <code>mpf_clear</code> or the full <code>mpf_set_prec</code>, another
<code>mpf_set_prec_raw</code> call must be made to restore <var>rop</var> to its original
allocated precision. Failing to do so will have unpredictable results.
</p>
<p><code>mpf_get_prec</code> can be used before <code>mpf_set_prec_raw</code> to get the
original allocated precision. After <code>mpf_set_prec_raw</code> it reflects the
<var>prec</var> value set.
</p>
<p><code>mpf_set_prec_raw</code> is an efficient way to use an <code>mpf_t</code> variable at
different precisions during a calculation, perhaps to gradually increase
precision in an iteration, or just to use various different precisions for
different purposes during a calculation.
</p></dd></dl>
<hr>
<div class="header">
<p>
Next: <a href="Assigning-Floats.html#Assigning-Floats" accesskey="n" rel="next">Assigning Floats</a>, Previous: <a href="Floating_002dpoint-Functions.html#Floating_002dpoint-Functions" accesskey="p" rel="prev">Floating-point Functions</a>, Up: <a href="Floating_002dpoint-Functions.html#Floating_002dpoint-Functions" accesskey="u" rel="up">Floating-point Functions</a> &nbsp; [<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>