Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r83622 - sandbox/precision/libs/precision/doc/html/precision
From: pbristow_at_[hidden]
Date: 2013-03-28 09:58:50

Next message: steven_at_[hidden]: "[Boost-commit] svn:boost r83623 - trunk/tools/build/v2"
Previous message: pbristow_at_[hidden]: "[Boost-commit] svn:boost r83621 - in sandbox/precision/libs/precision/doc: . html html/precision"

Author: pbristow
Date: 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
New Revision: 83622
URL: http://svn.boost.org/trac/boost/changeset/83622

Log:
Missing html
Added:
   sandbox/precision/libs/precision/doc/html/precision/cmathinterop.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/complexinteract.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/complexinterop.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/context.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/limitsinterop.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/literals.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/lowerprecision.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/microfpu.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/quadprecision.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/thestandard.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html (contents, props changed)
   sandbox/precision/libs/precision/doc/html/precision/thetypes.html (contents, props changed)

Added: sandbox/precision/libs/precision/doc/html/precision/cmathinterop.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/cmathinterop.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,75 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Interoperation with <cmath> and special functions</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="thestandard.html" title="Place in the standard">
+<link rel="next" href="limitsinterop.html" title="Interoperation with <limits>">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="thestandard.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="limitsinterop.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_cmathinterop">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.cmathinterop"></a><a class="link" href="cmathinterop.html" title="Interoperation with <cmath> and special functions">Interoperation with <cmath>
+ and special functions</a>
+</h2></div></div></div>
+
+ It is not proposed to make any mandatory changes to <code class="computeroutput"><cmath></code>
+ or special functions.
+ 
+
+ Any of the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width that are <code class="computeroutput">typedef</code>ed
+ from the built-in types <code class="computeroutput">float</code>,
+ <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ double</code> should automatically be supported
+ by the implementation's existing <code class="computeroutput"><cmath></code>
+ and special functions.
+ 
+
+ Implementation-specific optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width that are not derived from <code class="computeroutput">float</code>,
+ <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ double</code> can optionally be supported by
+ <code class="computeroutput"><cmath></code> and special functions. This is considered
+ an implementation detail.
+ 
+<div class="note"><table border="0" summary="Note">
+<tr>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
+<th align="left">Note</th>
+</tr>
+<tr><td align="left" valign="top">
+ Support of elementary functions (and possibly some special functions, even
+ where only optional) can be very useful for real-life computational regimes.
+ </td></tr>
+</table></div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="thestandard.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="limitsinterop.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/complexinteract.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/complexinteract.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,46 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Interaction with complex</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Types">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Types">
+<link rel="prev" href="precision/newfloattypes.html" title="Proposed new section">
+<link rel="next" href="microfpu.html" title="Improved efficiency and robustness for microcontrollers">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="precision/newfloattypes.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="microfpu.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_complexinteract">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.complexinteract"></a><a class="link" href="complexinteract.html" title="Interaction with complex">Interaction with complex</a>
+</h2></div></div></div>
+
+ TBD: Describe interaction with <complex>
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="precision/newfloattypes.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="microfpu.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/complexinterop.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/complexinterop.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,61 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Interoperation with <complex></title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="limitsinterop.html" title="Interoperation with <limits>">
+<link rel="next" href="quadprecision.html" title="Specifying 128-bit precision">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="limitsinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="quadprecision.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_complexinterop">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.complexinterop"></a><a class="link" href="complexinterop.html" title="Interoperation with <complex>">Interoperation with <complex></a>
+</h2></div></div></div>
+
+ It is not proposed to make any mandatory changes to <code class="computeroutput"><complex></code>.
+ 
+
+ Any of the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width that are <code class="computeroutput">typedef</code>ed
+ from the built-in types <code class="computeroutput">float</code>,
+ <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ double</code> should automatically be supported
+ by the implementation's existing <code class="computeroutput"><complex></code>.
+ 
+
+ Implementation-specific optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width that are not derived from <code class="computeroutput">float</code>,
+ <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ double</code> can optionally be
+ supported by <code class="computeroutput"><complex></code>. This is considered an implementation detail.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="limitsinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="quadprecision.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/context.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/context.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,52 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>The context among existing implementations</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="lowerprecision.html" title="Extending to lower precision">
+<link rel="next" href="references.html" title="References">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="lowerprecision.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="references.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_context">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.context"></a><a class="link" href="context.html" title="The context among existing implementations">The context among existing implementations</a>
+</h2></div></div></div>
+
+ Many existing implementations already support <code class="computeroutput">float</code>,
+ <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ double</code>. In addition, some of these either
+ are or strive to be compliant with <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>. In these cases, it will be straightforward to
+ support (at least) a subset of the proposed optional floating-point <code class="computeroutput">typedef</code>s having specified width by adding any
+ desired optional type definitions and the corresponding macro definitions.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="lowerprecision.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="references.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/limitsinterop.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/limitsinterop.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,91 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Interoperation with <limits></title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="cmathinterop.html" title="Interoperation with <cmath> and special functions">
+<link rel="next" href="complexinterop.html" title="Interoperation with <complex>">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="cmathinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="complexinterop.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_limitsinterop">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.limitsinterop"></a><a class="link" href="limitsinterop.html" title="Interoperation with <limits>">Interoperation with <limits></a>
+</h2></div></div></div>
+
+ It is not proposed to make any mandatory changes to <code class="computeroutput"><limits></code>.
+ 
+
+ Any of the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width that are <code class="computeroutput">typedef</code>ed
+ from the built-in types <code class="computeroutput">float</code>,
+ <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ double</code> should automatically be supported
+ by the implementation's existing <code class="computeroutput"><limits></code>.
+ 
+
+ Implementation-specific optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width that are not derived from <code class="computeroutput">float</code>,
+ <code class="computeroutput">double</code>, and <code class="computeroutput">long
+ double</code> can optionally be supported by
+ <code class="computeroutput"><limits></code>. This is considered an implementation detail.
+ 
+<div class="note"><table border="0" summary="Note">
+<tr>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
+<th align="left">Note</th>
+</tr>
+<tr><td align="left" valign="top">
+ Support for <code class="computeroutput"><limits></code>, even where optional, can be very useful,
+ especially for portability. This allows programs to query the floating-point
+ limits at compile-time and use, among other things, <code class="computeroutput">std::numeric_limits<>::is_iec559</code>
+ to verify conformance with <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>.
+ </td></tr>
+</table></div>
+<div class="note"><table border="0" summary="Note">
+<tr>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.png"></td>
+<th align="left">Note</th>
+</tr>
+<tr><td align="left" valign="top">
+ Each of the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width can only have <code class="computeroutput">true</code>
+ for the value of <code class="computeroutput">std::numeric_limits<>::is_iec559</code> if its underlying type (be it
+ <code class="computeroutput">float</code>, <code class="computeroutput">double</code>,
+ <code class="computeroutput">long double</code>
+ or an implementation-dependent type) conforms with one of <code class="computeroutput">binary16</code>,
+ <code class="computeroutput">binary32</code>, <code class="computeroutput">binary64</code>,
+ or <code class="computeroutput">binary128</code> in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>.
+ </td></tr>
+</table></div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="cmathinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="complexinterop.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/literals.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/literals.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,92 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Handling floating-point literals</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="thetypedefs.html" title="The proposed typedefs and potential extensions">
+<link rel="next" href="thestandard.html" title="Place in the standard">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="thetypedefs.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="thestandard.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_literals">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.literals"></a><a class="link" href="literals.html" title="Handling floating-point literals">Handling floating-point literals</a>
+</h2></div></div></div>
+
+ We will now examine how to use floating-point literal constants in combination
+ with the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width. This will be done in a manner analagous to the mechanism
+ specified for integer types having specified width, in other words using C-style
+ macros.
+ 
+
+ The header <code class="computeroutput"><cstdfloat></code> should contain all necessary C-style function
+ macros in the form shown below.
+ 
+<pre class="programlisting">FLOAT{16 32 64 128 256 MAX}_C
+</pre>
+
+ The code below, for example, initializes a constant <code class="computeroutput">float128_t</code>
+ value using one of these macros.
+ 
+<pre class="programlisting">#include <cstdfloat>
+
+constexpr std::float128_t euler = FLOAT128_C(0.57721566490153286060651209008240243104216);
+</pre>
+
+ The following code initializes a constant <code class="computeroutput">float16_t</code>
+ value using another one of these macros.
+ 
+<pre class="programlisting">#include <cstdfloat>
+
+constexpr std::float16_t euler = FLOAT16_C(0.577216);
+</pre>
+
+ In addition, the header <code class="computeroutput"><cstdfloat></code> should contain all necessary macros of
+ the form:
+ 
+<pre class="programlisting">FLOAT_[FAST LEAST]{16 32 64 128 256}_MIN
+FLOAT_[FAST LEAST]{16 32 64 128 256}_MAX
+FLOATMAX_MIN
+FLOATMAX_MAX
+</pre>
+
+ These macros can be used to query the ranges of the optional floating-point
+ <code class="computeroutput">typedef</code>s having specified width
+ at compile-time. For example,
+ 
+<pre class="programlisting">#include <limits>
+#include <cstdfloat>
+
+static_assert(FLOATMAX_MAX > (std::numeric_limits<float>::max)(),
+ "The floating-point range is too small.");
+</pre>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="thetypedefs.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="thestandard.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/lowerprecision.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/lowerprecision.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,67 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Extending to lower precision</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="quadprecision.html" title="Specifying 128-bit precision">
+<link rel="next" href="context.html" title="The context among existing implementations">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="quadprecision.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="context.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_lowerprecision">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.lowerprecision"></a><a class="link" href="lowerprecision.html" title="Extending to lower precision">Extending to lower precision</a>
+</h2></div></div></div>
+
+ Some implementations for cost-sensitive microcontroller platforms support
+ <code class="computeroutput">float</code>, <code class="computeroutput">double</code>,
+ and <code class="computeroutput">long double</code>,
+ and some of these are compliant with <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>. Some of these implementations treat <code class="computeroutput">double</code> exactly as <code class="computeroutput">float</code>,
+ and even treat <code class="computeroutput">long double</code>
+ exactly as <code class="computeroutput">double</code>. This is permitted
+ by the standard which does not prescribe the precision for any floating-point
+ (or integer) types, leaving them to be implementation-defined. On these platforms,
+ the existing floating-point types could optionally be type-defined to <code class="computeroutput">float32_t</code>. Optional support for an extension
+ to <code class="computeroutput">float16_t</code> could provide
+ a very useful and efficient floating-point type with half-precision, but reduced
+ range.
+ 
+
+ Some implementations for cost-sensitive microcontroller platforms also support
+ a 24-bit floating-point type. Here, an extension of the optional floating-point
+ <code class="computeroutput">typedef</code>s with specified width
+ could include <code class="computeroutput">float24_t</code>. This
+ would be equivalent to three-quarter precision floating-point, which is not
+ specified in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="quadprecision.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="context.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/microfpu.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/microfpu.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,63 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Improved efficiency and robustness for microcontrollers</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="complexinterop.html" title="Interoperation with <complex>">
+<link rel="next" href="context.html" title="The context within existing implementations">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="complexinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="context.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_microfpu">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.microfpu"></a><a class="link" href="microfpu.html" title="Improved efficiency and robustness for microcontrollers">Improved efficiency and robustness
+ for microcontrollers</a>
+</h2></div></div></div>
+
+ TBD by Chris: Describe cost-sensitive floating-point regime. TBD by Chris -
+ add reference to your book!
+ 
+
+ TBD by Chris: Describe recent confidential meetings with tier-one silicon suppliers
+ and the relevant problems discussed therein.
+ 
+
+ TBD: Cite these as personal communications.
+ 
+
+ TBD by Chris: Explain how standards adherence and specified width can help
+ to solve these problems by improving reliability and safety.
+ 
+
+ TBD ba Chris: Add an example and remarks on functional safety and any relevant
+ citations from to ISO/IEC 26262.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="complexinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="context.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/quadprecision.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/quadprecision.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,132 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Specifying 128-bit precision</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="complexinterop.html" title="Interoperation with <complex>">
+<link rel="next" href="lowerprecision.html" title="Extending to lower precision">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="complexinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="lowerprecision.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_quadprecision">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.quadprecision"></a><a class="link" href="quadprecision.html" title="Specifying 128-bit precision">Specifying 128-bit precision</a>
+</h2></div></div></div>
+
+ The proposed <code class="computeroutput">typedef</code> <code class="computeroutput">float128_t</code> provides a standardized way to
+ specify quadruple-precision (<a href="http://en.wikipedia.org/wiki/Quadruple-precision_floating-point_format" target="_top">Quadruple-precision
+ floating-point format</a>) in C++.
+ 
+
+ On powerful PCs and workstations, implementation-specific versions of <code class="computeroutput">long double</code>
+ as well as various floating-point extensions to 128-bit have been treated in
+ a variety of ways. This has resulted in numerous portability problems.
+ 
+
+ The Intel X8087 chipset
+ is capable of performing calculations with internal 80-bit registers. This
+ increases the width of the significand from 53 to 63 bits, thereby gaining
+ about 3 decimal digits precision and extending it from 18 and 21. If an implementation
+ has a type that uses all 80 bits from this chipset to calculate <a href="http://en.wikipedia.org/wiki/Extended_precision" target="_top">Extended
+ precision</a>, it could could use an optional <code class="computeroutput">typedef</code>
+ of this type to <code class="computeroutput">float80_t</code>.
+ 
+
+ Some hardware, for example Sparc,
+ provides a full 128-bit quadruple-precision floating-point chip. An implementation
+ for this kind of architecture might already have a built-in type corresponding
+ to <code class="computeroutput">binary128</code>, and this type
+ could be optionally <code class="computeroutput">typedef</code>ed
+ to <code class="computeroutput">float128_t</code>.
+ 
+
+ GCC has recently developed quadruple-precision support on a variety of platforms
+ using GCC libquadmath.
+ However, the implementation-specific type <code class="computeroutput">__float128</code>
+ is used rather than <code class="computeroutput">long double</code>.
+ These implementations could optionally <code class="computeroutput">typedef</code>
+ <code class="computeroutput">__float128</code> to <code class="computeroutput">float128_t</code> in addition to any other optional
+ <code class="computeroutput">typedef</code>s.
+ 
+
+ Darwin
+ <code class="computeroutput">long double</code>
+ uses a double-double format developed first by <a href="http://keithbriggs.info/doubledouble.html" target="_top">Keith
+ Briggs</a>. This gives about 106-bits of precision (about 33 decimal digits)
+ but has rather odd behavior at the extremes making implementation of <code class="computeroutput">std::numeric_limits<>::epsilon()</code> problematic.
+ 
+
+ It may be useful if future implementations for powerful PCs and workstations
+ strive to make implementation-specific extensions to 128-bit floating-point
+ or the built-in type <code class="computeroutput">long double</code>
+ equivalent to <code class="computeroutput">binary128</code>, and
+ to include the corresponding <code class="computeroutput">typedef</code>
+ to <code class="computeroutput">float128_t</code>.
+ 
+
+ Some architectures have hardware support for this. Those lacking direct hardware
+ support can use software emulation.
+ 
+<h5>
+<a name="precision.quadprecision.h0"></a>
+ <a name="precision.quadprecision.survey_of_extended_precision_types"></a><a class="link" href="quadprecision.html#precision.quadprecision.survey_of_extended_precision_types">Survey
+ of extended-precision types</a>
+ </h5>
+<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+ <a href="http://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html" target="_top">GNU
+ C supports additional floating types, <code class="computeroutput">__float80</code>
+ and <code class="computeroutput">__float128</code> to support
+ 80-bit (XFmode) and 128-bit (TFmode) floating types.</a>
+ </li>
+<li class="listitem">
+ <a href="http://software.intel.com/en-us/forums/topic/358472" target="_top">Extended
+ or Quad IEEE FP formats</a> by Intel Intel64 mode on Linux (V12.1)
+ provides 128 bit <code class="computeroutput">long double</code>
+ in C, however it appears that it only provides computation at 80-bit format
+ giving 64-bit significand precision, and other bits are just padding.
+ </li>
+<li class="listitem">
+ <a href="http://software.intel.com/en-us/forums/topic/358476" target="_top">Intel
+ FORTRAN REAL*16</a> is an actual 128-bit IEEE quad, emulated in software.
+ But "I don't know of any plan to implement full C support for 128-bit
+ IEEE format, although evidently ifort has support libraries." This
+ is equivalent to the proposed float128_t type.
+ </li>
+<li class="listitem">
+ The 360/85 and follow-on System/370 added support for a 128-bit "extended"
+ <a href="http://en.wikipedia.org/wiki/Extended_precision#IBM_extended_precision_formats" target="_top">IBM
+ extended precision formats</a>. These formats are still supported in
+ the current design, where they are now called the "hexadecimal floating
+ point" (HFP) formats.
+ </li>
+</ol></div>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="complexinterop.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="lowerprecision.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/thestandard.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/thestandard.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,114 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>Place in the standard</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="literals.html" title="Handling floating-point literals">
+<link rel="next" href="cmathinterop.html" title="Interoperation with <cmath> and special functions">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="literals.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="cmathinterop.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_thestandard">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.thestandard"></a><a class="link" href="thestandard.html" title="Place in the standard">Place in the standard</a>
+</h2></div></div></div>
+
+ The proper place for defining the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width should be oriented along the lines of the current standard.
+ Consider the existing specification of integer <code class="computeroutput">typedef</code>s
+ having specified width in C++11. A partial synopsis is shown below.
+ 
+
+ 18.4 Integer types [cstdint]
+ 
+
+ 18.4.1 Header <cstdint> synopsis [cstdint.syn]
+ 
+<pre class="programlisting">namespace std
+{
+ typedef signed integer type int8_t; // optional
+ typedef signed integer type int16_t; // optional
+ typedef signed integer type int32_t; // optional
+ typedef signed integer type int64_t; // optional
+}
+
+// ... and the corresponding least and fast types.
+</pre>
+
+ It is not immediately obvious where the optional floating-point <code class="computeroutput">typedef</code>s having specified width should reside.
+ One potential place is <code class="computeroutput"><cstdint></code>. The <code class="computeroutput">int</code>,
+ however, implies integer types. Here, we prefer the proposed new header <code class="computeroutput"><cstdfloat></code>.
+ 
+
+ We propose to add a new header <code class="computeroutput"><cstdfloat></code>
+ to the standard library. The header <code class="computeroutput"><cstdfloat></code>
+ should contain all optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width included in the implementation and the corresponding
+ C-style macros shown above.
+ 
+
+ Section 18.4 could be extended as shown below.
+ 
+
+ 18.4? Integer and Floating-Point Types Having Specified Width
+ 
+
+ 18.4.1 Header <cstdint> synopsis [cstdint.syn]
+ 
+
+ 18.4.2? Header <cstdfloat> synopsis [cstdfloat.syn]
+ 
+<pre class="programlisting">namespace std
+{
+ typedef floating-point type float16_t; // optional.
+ typedef floating-point type float32_t; // optional.
+ typedef floating-point type float64_t; // optional.
+ typedef floating-point type float80_t; // optional.
+ typedef floating-point type float128_t; // optional.
+ typedef floating-point type float256_t; // optional.
+ typedef floating-point type floatmax_t; // optional.
+
+ typedef floating-point type float_least16_t; // optional.
+ typedef floating-point type float_least32_t; // optional.
+ typedef floating-point type float_least64_t; // optional.
+ typedef floating-point type float_least80_t; // optional.
+ typedef floating-point type float_least128_t; // optional.
+ typedef floating-point type float_least256_t; // optional.
+
+ typedef floating-point type float_fast16_t; // optional.
+ typedef floating-point type float_fast32_t; // optional.
+ typedef floating-point type float_fast64_t; // optional.
+ typedef floating-point type float_fast80_t; // optional.
+ typedef floating-point type float_fast128_t; // optional.
+ typedef floating-point type float_fast256_t; // optional.
+}
+</pre>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="literals.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="cmathinterop.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,235 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>The proposed typedefs and potential extensions</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Typedefs">
+<link rel="prev" href="introduction.html" title="Introduction">
+<link rel="next" href="literals.html" title="Handling floating-point literals">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="introduction.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="literals.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_thetypedefs">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.thetypedefs"></a><a class="link" href="thetypedefs.html" title="The proposed typedefs and potential extensions">The proposed typedefs and potential
+ extensions</a>
+</h2></div></div></div>
+
+ The core of this proposal is based on the optional floating-point <code class="computeroutput">typedef</code>s <code class="computeroutput">float16_t</code>,
+ <code class="computeroutput">float32_t</code>, <code class="computeroutput">float64_t</code>,
+ <code class="computeroutput">float128_t</code>, their corresponding
+ least and fast types, and the corresponding maximum-width type.
+ 
+
+ For example,
+ 
+<pre class="programlisting">// Sample partial synopsis of <cstdfloat>
+
+namespace std
+{
+ typedef float float32_t;
+ typedef double float64_t;
+ typedef long double float128_t;
+ typedef float128_t floatmax_t;
+
+ // ... and the corresponding least and fast types.
+}
+</pre>
+
+ These proposed optional floating-point <code class="computeroutput">typedef</code>s
+ are to conform with the corresponding specifications of <code class="computeroutput">binary16</code>,
+ <code class="computeroutput">binary32</code>, <code class="computeroutput">binary64</code>,
+ and <code class="computeroutput">binary128</code> in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>. In particular, <code class="computeroutput">float16_t</code>,
+ <code class="computeroutput">float32_t</code>, <code class="computeroutput">float64_t</code>,
+ and <code class="computeroutput">float128_t</code> correspond to
+ floating-point types with 11, 24, 53, and 113 binary significand digits, respectively.
+ These are defined in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>, and there are more detailed descriptions of
+ each type at <a href="http://en.wikipedia.org/wiki/Half_precision_floating-point_format" target="_top">IEEE
+ half-precision floating-point format</a>, <a href="http://en.wikipedia.org/wiki/Single_precision_floating-point_format" target="_top">IEEE
+ single-precision floating-point format</a>, <a href="http://en.wikipedia.org/wiki/Double_precision_floating-point_format" target="_top">IEEE
+ double-precision floating-point format</a>, <a href="http://en.wikipedia.org/wiki/Quadruple-precision_floating-point_format" target="_top">Quadruple-precision
+ floating-point format</a>, and <a href="http://en.wikipedia.org/wiki/Extended_precision#IEEE_754_extended_precision_formats" target="_top">IEEE
+ 754 extended precision formats and x86 80-bit Extended Precision Format</a>.
+ 
+
+ Here, we specifically mean equivalence of the following.
+ 
+<pre class="programlisting">float16_t == binary16;
+float32_t == binary32;
+float64_t == binary64;
+float128_t == binary128;
+</pre>
+
+ This equivalence results in far-reaching benefits.
+ 
+
+ It means that floating-point software written with <code class="computeroutput">float16_t</code>,
+ <code class="computeroutput">float32_t</code>, <code class="computeroutput">float64_t</code>,
+ and <code class="computeroutput">float128_t</code> should behave
+ identically when used on any platform with any implementation that correctly
+ supports the <code class="computeroutput">typedef</code>s.
+ 
+
+ It also creates the opportunity to implement quadruple-precision (<a href="http://en.wikipedia.org/wiki/Quadruple-precision_floating-point_format" target="_top">Quadruple-precision
+ floating-point format</a>) in a specified, and therefore portable, fashion.
+ 
+
+ One could envision two ways to name the proposed optional floating-point <code class="computeroutput">typedef</code>s having specified width:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <code class="computeroutput">float11_t,
+ float24_t,
+ float53_t,
+ float113_t,
+ ...</code>
+ </li>
+<li class="listitem">
+ <code class="computeroutput">float16_t,
+ float32_t,
+ float64_t,
+ float128_t,
+ ...</code>
+ </li>
+</ul></div>
+
+ The first set above is intuitively coined from IEE754:2008.
+ It is also consistent with the gist of integer types having specified width
+ such as <code class="computeroutput">int64_t</code>, in so far
+ as the number of binary digits of significand precision
+ is contained within the name of the data type.
+ 
+
+ On the other hand, the second set with the size of the whole type
+ contained within the name may be more intuitive to users. Here, we prefer the
+ latter naming scheme.
+ 
+
+ No matter what naming scheme is used, the exact layout and number of significand
+ and exponent bits can be confirmed as IEEE754 by checking <code class="computeroutput">std::numeric_limits<type>::is_iec559
+ == true</code>,
+ and the byte-order.
+ 
+
+ We will now consider several examples showing how various implementations might
+ introduce some of the optional floating-point <code class="computeroutput">typedef</code>s
+ having specified width into the <code class="computeroutput">std</code>
+ namespace.
+ 
+
+ An implementation has <code class="computeroutput">float</code> and
+ <code class="computeroutput">double</code> corresponding to IEEE754
+ <code class="computeroutput">binary32</code>, <code class="computeroutput">binary64</code>,
+ respectively. This implementation could introduce <code class="computeroutput">float32_t</code>,
+ <code class="computeroutput">float64_t</code>, and <code class="computeroutput">floatmax_t</code> into the <code class="computeroutput">std</code>
+ namespace as shown below.
+ 
+<pre class="programlisting">// In <cstdfloat>
+
+namespace std
+{
+ typedef float float32_t;
+ typedef double float64_t;
+ typedef float64_t floatmax_t;
+}
+</pre>
+
+ There may be a need for octuple-precision float, in other words an extension
+ to <code class="computeroutput">float256_t</code> with about 240
+ binary significand digits of precision. In addition, a <code class="computeroutput">float512_t</code>
+ type with even more precision may be considered as a option. Beyond these,
+ there may be potential extension to multiprecision types, even <a href="http://en.wikipedia.org/wiki/Arbitrary_precision" target="_top">arbitrary
+ precision</a>, in the future.
+ 
+
+ Consider an implementation for a supercomputer. This platform might have <code class="computeroutput">float</code>, <code class="computeroutput">double</code>,
+ and <code class="computeroutput">long double</code>
+ corresponding to IEEE754 <code class="computeroutput">binary32</code>,
+ <code class="computeroutput">binary64</code>, and <code class="computeroutput">binary128</code>, respectively. In addition, this
+ platform might have a floating-point type with octuple-precision. The implementation
+ for this supercomputer could introduce its optional floating-point <code class="computeroutput">typedef</code>s having specified width into the <code class="computeroutput">std</code> namespace as shown below.
+ 
+<pre class="programlisting">// In <cstdfloat>
+
+namespace std
+{
+ typedef float float32_t;
+ typedef double float64_t;
+ typedef long double float128_t;
+ typedef floating-point type float256_t;
+ typedef float256_t floatmax_t;
+}
+</pre>
+
+ A cost-sensitive 8-bit microcontroller platform without an FPU does not have
+ sufficient resources to support the eight-byte, 64-bit <code class="computeroutput">binary64</code>
+ type in a feasible fashion. An implementation for this platform can, however,
+ support half-precision <code class="computeroutput">float16_t</code>
+ and single-precision <code class="computeroutput">float32_t</code>.
+ This implementation could introduce its optional floating-point <code class="computeroutput">typedef</code>s having specified width into the <code class="computeroutput">std</code> namespace as shown below.
+ 
+<pre class="programlisting">// In <cstdfloat>
+
+namespace std
+{
+ typedef floating-point type float16_t;
+ typedef float float32_t;
+ typedef float32_t floatmax_t;
+}
+</pre>
+
+ The popular Intel X8087 chipset
+ architecture supports a 10-byte floating-point format. It may be useful to
+ extend the optional support to <code class="computeroutput">float80_t</code>.
+ Several implementations using <a href="http://en.wikipedia.org/wiki/Extended_precision#IEEE_754_extended_precision_formats#" target="_top">x86
+ Extended Precision Format</a> already exist in practice.
+ 
+
+ Consider an implementation that supports single-precision <code class="computeroutput">float</code>,
+ double-precision <code class="computeroutput">double</code>, and 10-byte
+ <code class="computeroutput">long double</code>.
+ This implementation could introduce its optional <code class="computeroutput">typedef</code>s
+ <code class="computeroutput">float32_t</code>, <code class="computeroutput">float64_t</code>,
+ <code class="computeroutput">float80_t</code>, and <code class="computeroutput">floatmax_t</code> into the <code class="computeroutput">std</code>
+ namespace as shown below.
+ 
+<pre class="programlisting">// In <cstdfloat>
+
+namespace std
+{
+ typedef float float32_t;
+ typedef double float64_t;
+ typedef long double float80_t;
+ typedef float80_t floatmax_t;
+}
+</pre>
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="introduction.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="literals.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Added: sandbox/precision/libs/precision/doc/html/precision/thetypes.html
==============================================================================
--- (empty file)
+++ sandbox/precision/libs/precision/doc/html/precision/thetypes.html 2013-03-28 09:58:49 EDT (Thu, 28 Mar 2013)
@@ -0,0 +1,229 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
+<title>The proposed types and potential extensions</title>
+<link rel="stylesheet" href=".././boostbook.css" type="text/css">
+<meta name="generator" content="DocBook XSL Stylesheets V1.77.1">
+<link rel="home" href="../index.html" title="Specific-Width Floating-Point Types">
+<link rel="up" href="../index.html" title="Specific-Width Floating-Point Types">
+<link rel="prev" href="introduction.html" title="Introduction">
+<link rel="next" href="suffixes.html" title="How to define floating-point literal suffixes?">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table cellpadding="2" width="100%"><tr>
+<td valign="top"><img alt="" width="180" height="90" src=".././images/boost.png"></td>
+<td align="center">Home</td>
+<td align="center">Libraries</td>
+<td align="center">People</td>
+<td align="center">FAQ</td>
+<td align="center">More</td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="introduction.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="suffixes.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+<div class="section precision_thetypes">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="precision.thetypes"></a><a class="link" href="thetypes.html" title="The proposed types and potential extensions">The proposed types and potential extensions</a>
+</h2></div></div></div>
+
+ The core of this proposal is based on the types <code class="computeroutput">float16_t</code>,
+ <code class="computeroutput">float32_t</code>, <code class="computeroutput">float64_t</code>,
+ <code class="computeroutput">float128_t</code>, and their corresponding
+ least and fast types. These floating-point types have specified widths and
+ they are to conform with the corresponding types <code class="computeroutput">binary16</code>,
+ <code class="computeroutput">binary32</code>, <code class="computeroutput">binary64</code>,
+ and <code class="computeroutput">binary128</code> specified in
+ <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_ floating-point
+ format</a>. In particular, <code class="computeroutput">float16_t</code>,
+ <code class="computeroutput">float32_t</code>, <code class="computeroutput">float64_t</code>,
+ and <code class="computeroutput">float128_t</code> correspond to
+ floating-point types with 11, 24, 53, and 113 binary significand digits, respectively.
+ These are defined in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>, and there are more detailed descrptions of each
+ type at <a href="http://en.wikipedia.org/wiki/Half_precision_floating-point_format" target="_top">IEEE
+ half-precision floating-point format</a>, <a href="http://en.wikipedia.org/wiki/Single_precision_floating-point_format" target="_top">IEEE
+ single-precision floating-point format</a>, <a href="http://en.wikipedia.org/wiki/Double_precision_floating-point_format" target="_top">IEEE
+ double-precision floating-point format</a>, <a href="http://en.wikipedia.org/wiki/Quadruple-precision_floating-point_format" target="_top">Quadruple-precision
+ floating-point format</a>, and <a href="http://en.wikipedia.org/wiki/Extended_precision#IEEE_754_extended_precision_formats" target="_top">IEEE
+ 754 extended precision formats and x86 80-bit Extended Precision Format</a>.
+ 
+
+ One could envision two ways to name the proposed floating-point types having
+ specified width:
+ 
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <code class="computeroutput">float11_t,
+ float24_t,
+ float53_t,
+ float113_t,
+ ...</code>
+ </li>
+<li class="listitem">
+ <code class="computeroutput">float16_t,
+ float32_t,
+ float64_t,
+ float128_t,
+ ...</code>
+ </li>
+</ul></div>
+
+ The first set above is intuitively coined from IEE754:2008.
+ It is also consistent with the gist of integer types having specified width
+ such as <code class="computeroutput">int64_t</code>, in so far
+ as the number of binary digits of significand precision
+ is contained within the name of the data type.
+ 
+
+ On the other hand, the second set with the size of the whole type
+ contained within the name may be more intuitive to users. Here, we prefer this
+ naming scheme.
+ 
+
+ No matter what naming scheme is used, the exact layout and number of significand
+ and exponent bits can be confirmed as IEEE754 by checking <code class="computeroutput">std::numeric_limits<type>::is_iec559
+ == true</code>.
+ 
+
+ We will now consider several examples showing how various implementations might
+ include floating-point types having specified width.
+ 
+
+ An implementation that has <code class="computeroutput">float</code>
+ and <code class="computeroutput">double</code> corresponding to IEEE
+ 754 <code class="computeroutput">binary32</code>, <code class="computeroutput">binary64</code>, respectively, could introduce
+ <code class="computeroutput">float32_t</code> and <code class="computeroutput">float64_t</code> into the <code class="computeroutput">std</code>
+ namespace as shown below.
+ 
+<pre class="programlisting">namespace std
+{
+ typedef float float32_t;
+ typedef double float64_t;
+}
+</pre>
+
+ There may be a need for octuple-precision float, in other words <code class="computeroutput">float256_t</code> with about 240 binary significand
+ digits of precision. In addition, a <code class="computeroutput">float512_t</code>
+ type with even more precision may be considered as a option. Beyond these,
+ there may be potential extension to multiprecision types in the future.
+ 
+
+ Consider an implementation for a supercomputer. This platform might have <code class="computeroutput">float</code>, <code class="computeroutput">double</code>,
+ and <code class="computeroutput">long double</code>
+ corresponding to IEEE 754 <code class="computeroutput">binary32</code>,
+ <code class="computeroutput">binary64</code>, and <code class="computeroutput">binary128</code>, respectively. In addition, this
+ platform might have a user-defined type with octuple-precision. The implementation
+ for this supercomputer could introduce floating-point types having specified
+ width into the <code class="computeroutput">std</code> namespace
+ as shown below.
+ 
+<pre class="programlisting">namespace std
+{
+ typedef float float32_t;
+ typedef double float64_t;
+ typedef long double float128_t;
+ typedef my_octuple_precision_type float256_t;
+}
+</pre>
+
+ A cost-sensitive 8-bit microcontroller platform without an FPU does not have
+ sufficient resources to support eight-byte <code class="computeroutput">binary64</code>
+ in a feasible fashion. An implementation on this platform can, however, support
+ half-precision <code class="computeroutput">float16_t</code> and
+ single-precision <code class="computeroutput">float32_t</code>.
+ The implementation for this 8-bit microcontroller could introduce floating-point
+ types having specified width into the <code class="computeroutput">std</code>
+ namespace as shown below.
+ 
+<pre class="programlisting">namespace std
+{
+ typedef my_half_precision_type float16_t;
+ typedef float float32_t;
+}
+</pre>
+
+ The popular Intel X8087 chipset
+ architecture supports a 10-byte floating-point format. So it may be useful
+ to provide optional support for <code class="computeroutput">float80_t</code>.
+ In our opinion, there is no type that is analogous to <code class="computeroutput">float80_t</code>
+ in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_ floating-point
+ format</a>, but several implementations already exist in practice.
+ 
+
+ An implementation that supports single-precision <code class="computeroutput">float</code>,
+ double-precision <code class="computeroutput">double</code>, and 10-byte
+ <code class="computeroutput">long double</code>
+ could introduce <code class="computeroutput">float32_t</code>,
+ <code class="computeroutput">float64_t</code>, and <code class="computeroutput">float80_t</code> into the <code class="computeroutput">std</code>
+ namespace as shown below.
+ 
+<pre class="programlisting">namespace std
+{
+ typedef float float32_t;
+ typedef double float64_t;
+ typedef long double float80_t;
+}
+</pre>
+
+ We will now examine how to use floating-point literal constants in combination
+ with floating-point types having specified width.
+ 
+
+ At present, the only way to provide a floating-point literal constant value
+ with precision exceeding the precision of <code class="computeroutput">long
+ double</code> is to use a character string
+ in association with type conversion for a user-defined extended-precision type.
+ For example, construction from a string as well as the <code class="computeroutput">from_string</code>
+ method are used for this purpose in Boost.Math,
+ Boost.Multiprecision
+ and GCC libquadmath.
+ 
+
+ The sample below, for instance, uses the <code class="computeroutput">cpp_dec_float_50</code>
+ type from Boost.Multiprecision
+ to initialize the Euler-gamma constant with 50 decimal digits of precision.
+ 
+<pre class="programlisting">#include <boost/multiprecision/cpp_dec_float>
+
+typedef boost::multiprecision::cpp_dec_float_50 mp_type;
+
+const mp_type euler("0.577215664901532860606512090082402431042159335939924");
+</pre>
+
+ Construction from string is inappropriate for the proposed floating-point types
+ having specified width. These should be copy assignable and copy constructable
+ from floating-point literal constants. This requires slight changes to the
+ core language including the addition of new floating-point literal constant
+ suffixes. For instance, the sample below uses a potential <code class="computeroutput">Q</code>
+ suffix is used to initialize the Euler-gamma constant stored in a <code class="computeroutput">float128_t</code>.
+ 
+<pre class="programlisting">#include <cstdfloat>
+
+constexpr std::float128_t euler = 0.57721566490153286060651209008240243104216Q;
+</pre>
+
+ Suffixes will be described in greater detail below.
+ 
+
+ It would also be useful to have a method of querying the size of types, similar
+ to that provided by <a href="http://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html" target="_top">GCC
+ 3.7.2 Common Predefined Macros</a>, for example, <code class="computeroutput">__SIZEOF_LONG_DOUBLE__</code>.
+ But similar macros are not defined for <code class="computeroutput">__float128</code>
+ nor for <code class="computeroutput">__float80</code>.
+ 
+</div>
+<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
+<td align="left"></td>
+<td align="right"><div class="copyright-footer">Copyright © 2013 Paul A. Bristow, Christopher Kormanyos, John Maddock
+ Distributed under the Boost Software License, Version 1.0. (See accompanying
+ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
+ 
+</div></td>
+</tr></table>
+<hr>
+<div class="spirit-nav">
+<a accesskey="p" href="introduction.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="suffixes.html"><img src="../images/next.png" alt="Next"></a>
+</div>
+</body>
+</html>

Next message: steven_at_[hidden]: "[Boost-commit] svn:boost r83623 - trunk/tools/build/v2"
Previous message: pbristow_at_[hidden]: "[Boost-commit] svn:boost r83621 - in sandbox/precision/libs/precision/doc: . html html/precision"

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk