|
|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r83562 - in sandbox/precision/libs/precision/doc: . html html/precision
From: pbristow_at_[hidden]
Date: 2013-03-25 14:56:12
Author: pbristow
Date: 2013-03-25 14:56:11 EDT (Mon, 25 Mar 2013)
New Revision: 83562
URL: http://svn.boost.org/trac/boost/changeset/83562
Log:
R-built html and pdf
Binary files modified:
sandbox/precision/libs/precision/doc/precision.pdf
sandbox/precision/libs/precision/doc/precision.tws
Text files modified:
sandbox/precision/libs/precision/doc/html/index.html | 15 ++---
sandbox/precision/libs/precision/doc/html/precision/abstract.html | 61 +++++++++++------------
sandbox/precision/libs/precision/doc/html/precision/introduction.html | 102 +++++++++++++++++++--------------------
sandbox/precision/libs/precision/doc/html/precision/references.html | 7 ++
sandbox/precision/libs/precision/doc/html/precision/version_id.html | 2
sandbox/precision/libs/precision/doc/precision.qbk | 2
6 files changed, 93 insertions(+), 96 deletions(-)
Modified: sandbox/precision/libs/precision/doc/html/index.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/index.html (original)
+++ sandbox/precision/libs/precision/doc/html/index.html 2013-03-25 14:56:11 EDT (Mon, 25 Mar 2013)
@@ -48,19 +48,16 @@
<p><b>Table of Contents</b></p>
<dl>
<dt><span class="section">Abstract</span></dt>
-<dt><span class="section">Background</span></dt>
<dt><span class="section">Introduction</span></dt>
<dt><span class="section"><a href="precision/thetypedefs.html">The proposed typedefs and potential
extensions</a></span></dt>
-<dt><span class="section"><a href="precision/suffixes.html">How to define floating-point literal
- suffixes?</a></span></dt>
+<dt><span class="section">Handling floating-point literals</span></dt>
<dt><span class="section">Place in the standard</span></dt>
-<dt><span class="section">Interaction with <limits></span></dt>
-<dt><span class="section">Interoperation with <cmath></span></dt>
+<dt><span class="section"><a href="precision/cmathinterop.html">Interoperation with <cmath>
+ and special functions</a></span></dt>
+<dt><span class="section">Interoperation with <limits></span></dt>
<dt><span class="section">Interoperation with <complex></span></dt>
-<dt><span class="section"><a href="precision/microfpu.html">Improved efficiency and robustness
- for microcontrollers</a></span></dt>
-<dt><span class="section">The context within existing implementations</span></dt>
+<dt><span class="section">The context among existing implementations</span></dt>
<dt><span class="section">References</span></dt>
<dt><span class="section">Version Info</span></dt>
</dl>
@@ -79,7 +76,7 @@
</table></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"><p><small>Last revised: March 25, 2013 at 09:47:14 GMT</small></p></td>
+<td align="left"><p><small>Last revised: March 25, 2013 at 18:50:55 GMT</small></p></td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>
Modified: sandbox/precision/libs/precision/doc/html/precision/abstract.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/abstract.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/abstract.html 2013-03-25 14:56:11 EDT (Mon, 25 Mar 2013)
@@ -7,7 +7,7 @@
<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="../index.html" title="Specific-Width Floating-Point Typedefs">
-<link rel="next" href="background.html" title="Background">
+<link rel="next" href="introduction.html" title="Introduction">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr>
@@ -20,62 +20,59 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.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="background.html"><img src="../images/next.png" alt="Next"></a>
+<a accesskey="p" href="../index.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="introduction.html"><img src="../images/next.png" alt="Next"></a>
</div>
<div class="section precision_abstract">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="precision.abstract"></a><a class="link" href="abstract.html" title="Abstract">Abstract</a>
</h2></div></div></div>
<p>
- It is proposed to add to the C++ standard several optional typedefs for floating-point
- types having specified width. In particular, the optional types include <code class="computeroutput"><span class="identifier">float16_t</span></code>, <code class="computeroutput"><span class="identifier">float32_t</span></code>,
+ It is proposed to add to the C++ standard optional floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s having specified width. The optional
+ <code class="computeroutput"><span class="keyword">typedef</span></code>s include <code class="computeroutput"><span class="identifier">float16_t</span></code>, <code class="computeroutput"><span class="identifier">float32_t</span></code>,
<code class="computeroutput"><span class="identifier">float64_t</span></code>, <code class="computeroutput"><span class="identifier">float128_t</span></code>,
- and their corresponding fast and least types. The optional floating-point types
- are to conform with the corresponding types <code class="computeroutput"><span class="identifier">binary16</span></code>,
- <code class="computeroutput"><span class="identifier">binary32</span></code>, <code class="computeroutput"><span class="identifier">binary64</span></code>,
- and <code class="computeroutput"><span class="identifier">binary128</span></code> described in
- <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_ floating-point
- format</a>.
+ their corresponding fast and least types, and the corresponding maximum-width
+ type. These are to conform with the corresponding specifications of <code class="computeroutput"><span class="identifier">binary16</span></code>, <code class="computeroutput"><span class="identifier">binary32</span></code>,
+ <code class="computeroutput"><span class="identifier">binary64</span></code>, and <code class="computeroutput"><span class="identifier">binary128</span></code> in <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
+ floating-point format</a>.
</p>
<p>
- The optional floating-point types having specified width are to be contained
- in a new standard library header <code class="computeroutput"><span class="special"><</span><span class="identifier">cstdfloat</span><span class="special">></span></code>.
- Any of the optional floating-point types having specified width included in
- the implementation should have full support for the functions in <code class="computeroutput"><span class="special"><</span><span class="identifier">cmath</span><span class="special">></span></code> and seamlessly interoperate with <code class="computeroutput"><span class="special"><</span><span class="identifier">complex</span><span class="special">></span></code>. Any of the optional floating-point types
- having specified width included in the implementation must template specializations
- of <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">numeric_limits</span></code> in <code class="computeroutput"><span class="special"><</span><span class="identifier">limits</span><span class="special">></span></code>.
- The proposed new floating-point types having specified width will be defined
- in the global and <code class="computeroutput"><span class="identifier">std</span></code> namespaces.
+ The optional floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s
+ having specified width are to be contained in a new standard library header
+ <code class="computeroutput"><span class="special"><</span><span class="identifier">cstdfloat</span><span class="special">></span></code>. They will be defined in the <code class="computeroutput"><span class="identifier">std</span></code> namespace.
</p>
<p>
- It is also proposed to provide additional suffix(es) to specify constants to
- suit precision lower than that of <code class="computeroutput"><span class="keyword">float</span></code>
- and precision higher than that of <code class="computeroutput"><span class="keyword">long</span>
- <span class="keyword">double</span></code>.
+ It is not proposed to make any changes to <code class="computeroutput"><span class="special"><</span><span class="identifier">cmath</span><span class="special">></span></code>,
+ special functions, <code class="computeroutput"><span class="special"><</span><span class="identifier">limits</span><span class="special">></span></code>, or <code class="computeroutput"><span class="special"><</span><span class="identifier">complex</span><span class="special">></span></code>.
+ Any of the optional floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s
+ having specified width that are <code class="computeroutput"><span class="keyword">typedef</span></code>ed
+ from the built-in types <code class="computeroutput"><span class="keyword">float</span></code>,
+ <code class="computeroutput"><span class="keyword">double</span></code>, and <code class="computeroutput"><span class="keyword">long</span>
+ <span class="keyword">double</span></code> should automatically be supported
+ by the implementation's existing <code class="computeroutput"><span class="special"><</span><span class="identifier">cmath</span><span class="special">></span></code>,
+ special functions, <code class="computeroutput"><span class="special"><</span><span class="identifier">limits</span><span class="special">></span></code>, and <code class="computeroutput"><span class="special"><</span><span class="identifier">complex</span><span class="special">></span></code>.
+ Support for other <code class="computeroutput"><span class="keyword">typedef</span></code>s is
+ implementation-defined.
</p>
<p>
- Floating-point types having specified width are expected to significantly improve
- clarity of code and portability of floating-point calculations. Analogous improvements
- for integer calculations were recently achieved via standardization of integer
- types having specified width such as <code class="computeroutput"><span class="identifier">int8_t</span></code>,
- <code class="computeroutput"><span class="identifier">int16_t</span></code>, <code class="computeroutput"><span class="identifier">int32_t</span></code>,
- and <code class="computeroutput"><span class="identifier">int64_t</span></code>.
+ New C-style macros are proposed to facilitate initialization of the optional
+ floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s having
+ specified width from a floating-point literal constant.
</p>
<p>
The main objectives of this proposal are to:
</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">
- Extend the range of floating-point precision.
+ Improve portability, reliability and safety.
</li>
<li class="listitem">
- Reduce errors in precision.
+ Reduce the risk of error in precision.
</li>
<li class="listitem">
Improve clarity of coding.
</li>
<li class="listitem">
- Improve portability, reliability and safety.
+ Optionally extend the range of floating-point precision.
</li>
</ul></div>
</div>
@@ -89,7 +86,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="../index.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="background.html"><img src="../images/next.png" alt="Next"></a>
+<a accesskey="p" href="../index.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="introduction.html"><img src="../images/next.png" alt="Next"></a>
</div>
</body>
</html>
Modified: sandbox/precision/libs/precision/doc/html/precision/introduction.html
Modified: sandbox/precision/libs/precision/doc/html/precision/references.html
Modified: sandbox/precision/libs/precision/doc/html/precision/version_id.html
Modified: sandbox/precision/libs/precision/doc/precision.pdf
Modified: sandbox/precision/libs/precision/doc/precision.qbk
Modified: sandbox/precision/libs/precision/doc/precision.tws
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
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/introduction.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/introduction.html 2013-03-25 14:56:11 EDT (Mon, 25 Mar 2013)
@@ -6,7 +6,7 @@
<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="background.html" title="Background">
+<link rel="prev" href="abstract.html" title="Abstract">
<link rel="next" href="thetypedefs.html" title="The proposed typedefs and potential extensions">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -20,7 +20,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="background.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="thetypedefs.html"><img src="../images/next.png" alt="Next"></a>
+<a accesskey="p" href="abstract.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="thetypedefs.html"><img src="../images/next.png" alt="Next"></a>
</div>
<div class="section precision_introduction">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
@@ -35,65 +35,61 @@
for floating-point calculations in the programming community.
</p>
<p>
+ Support for mathematical facilities and specialized number types in C++ is
+ progressing rapidly. Currently, C++11 supports floating-point calculations
+ with its built-in types <code class="computeroutput"><span class="keyword">float</span></code>,
+ <code class="computeroutput"><span class="keyword">double</span></code>, and <code class="computeroutput"><span class="keyword">long</span>
+ <span class="keyword">double</span></code> as well as imlementations of
+ numerous elementary and transcendental functions.
+ </p>
+<p>
+ A variety of higher transcendental functions of pure and applied mathematics
+ were added to the C++11 libraries via technical report TR1. It is now proposed
+ to fix these into the next C++1Y standard.[1]</sup></a>
+ </p>
+<p>
+ Other mathematical special functions are also now proposed, for example, <a href="http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3494.pdf" target="_top">A proposal
+ to add special mathematical functions according to the ISO/IEC 80000-2:2009
+ standard Document number: N3494 Version: 1.0 Date: 2012-12-19</a>
+ </p>
+<p>
It is, however, emphasized that floating-point adherence to <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
floating-point format</a> is not mandated by the current C++ language standard.
- Nor does the standard specify the widths, precisions or lyaout of its built-in
+ Nor does the standard specify the width, precision or lyaout of its built-in
types <code class="computeroutput"><span class="keyword">float</span></code>, <code class="computeroutput"><span class="keyword">double</span></code>,
and <code class="computeroutput"><span class="keyword">long</span> <span class="keyword">double</span></code>.
This can lead to portability problems, introduce poor efficiency on cost-sensitive
microcontroller architectures, and reduce reliability and safety.
</p>
<p>
- This situation reveals a need for a standard way to specify precision. It is
- also desirable to extend the precision of existing types to both lower and
- higher precisions. The extension to lower precision is expected to simplify
- and improve efficiency of floating-point implementations on cost-sensitive
- architectures such as small microcontrollers. The extension to higher precision
- is useful for large-scale high-performance numerical calculations and should
- ease the transition to multiprecision by providing built-in types with progressing
- precision of finer granularity.
- </p>
-<p>
- All of these improvements should improve portability, reliability, and safety
- of floating-point calculations in C++ by ensuring that the actual precision
- of a floating-point type can be exactly determined both at compile-time as
- well as during the run of a calculation. Strong interest in floating-point
- <code class="computeroutput"><span class="identifier">typedefs</span></code> having specified width
- has, for example, recently been expressed on the <a href="http://lists.boost.org/Archives/boost/2013/03/201786.php" target="_top">Boost
- list discussion of precise floating-point types</a>.
- </p>
-<p>
- Recent specification of integer typedefs having specified width in C99, C11,
- C++11, and <a href="http://open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3376.pdf" target="_top">C++
- draft specification</a> has drastically improved integer algorithm portability
- and range.
- </p>
-<p>
- One example of how integer typedefs having specified width have proven to be
- essential is described by Robert Ramey <a href="http://lists.boost.org/Archives/boost/2002/11/40432.php" target="_top">Usefulness
- of fixed integer sizes in portability (for Boost serialization library).</a>
- </p>
-<p>
- The motivations to provide floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s
- having specified width are analogous to those that led to the introduction
- of integers having specified width such as <code class="computeroutput"><span class="identifier">int8_t</span></code>,
- <code class="computeroutput"><span class="identifier">int16_t</span></code>, <code class="computeroutput"><span class="identifier">int32_t</span></code>,
- and <code class="computeroutput"><span class="identifier">int64_t</span></code>. The specification
- of floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s having
- specified width and adherence to <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
- floating-point format</a> can potentially improve the C++ language significantly,
- especially in the scientific and engineering communities where other languages
- have found benefit from types that conform exactly to the <a href="http://en.wikipedia.org/wiki/IEEE_floating_point" target="_top">IEEE_
- floating-point format</a>.
- </p>
-<p>
- (Notes on jargon: Section 22.3 in the book "The C++ Standard Library Extensions",
- P. Becker, Addison Wesley 2007, ISBN 0-321-41299-0 is called "Fixed-Size
- Integer Types". Use of the descriptor <span class="emphasis"><em>fixed</em></span> has lead
- to some confusion. So the descriptor <span class="emphasis"><em>specific</em></span> in conjunction
- with width is here used to match the wording of C99 and C11 in the sections
- and subsections describing <code class="computeroutput"><span class="identifier">stdint</span><span class="special">.</span><span class="identifier">h</span></code>.)
+ This situation reveals a need for a standard way to specify floating-point
+ precision in C++.
+ </p>
+<p>
+ It may also be desirable to extend floating-point precision to both lower and
+ higher precisions. This can be done by including implementation-specific optional
+ floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s having
+ specified width that are not derived from <code class="computeroutput"><span class="keyword">float</span></code>,
+ <code class="computeroutput"><span class="keyword">double</span></code>, and <code class="computeroutput"><span class="keyword">long</span>
+ <span class="keyword">double</span></code>.
</p>
+<p>
+ Providing optional floating-point <code class="computeroutput"><span class="keyword">typedef</span></code>s
+ having specified width is expected to significantly improve portability, reliability,
+ and safety of floating-point calculations in C++. [2]</sup></a> ]
+ </p>
+<div class="footnotes">
+<br><hr style="width:100; align:left;">
+<div id="ftn.precision.introduction.f0" class="footnote"><p>[1]
+ <a href="http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3548.pdf" target="_top">Conditionally-supported
+ Special Math Functions for C++14, N3584, Walter E. Brown</a>
+ </p></div>
+<div id="ftn.precision.introduction.f1" class="footnote"><p>[2]
+ [Analogous improvements for integer calculations were recently achieved via
+ standardization of integer types having specified width such as <code class="computeroutput"><span class="identifier">int8_t</span></code>, <code class="computeroutput"><span class="identifier">int16_t</span></code>,
+ <code class="computeroutput"><span class="identifier">int32_t</span></code>, and <code class="computeroutput"><span class="identifier">int64_t</span></code>.
+ </p></div>
+</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
@@ -105,7 +101,7 @@
</tr></table>
<hr>
<div class="spirit-nav">
-<a accesskey="p" href="background.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="thetypedefs.html"><img src="../images/next.png" alt="Next"></a>
+<a accesskey="p" href="abstract.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="thetypedefs.html"><img src="../images/next.png" alt="Next"></a>
</div>
</body>
</html>
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/references.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/references.html 2013-03-25 14:56:11 EDT (Mon, 25 Mar 2013)
@@ -6,7 +6,7 @@
<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="context.html" title="The context within existing implementations">
+<link rel="prev" href="context.html" title="The context among existing implementations">
<link rel="next" href="version_id.html" title="Version Info">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -76,6 +76,11 @@
<li class="listitem">
<a href="http://gcc.gnu.org/wiki/x87note" target="_top">X8087 notes</a>
</li>
+<li class="listitem">
+ <a href="http://software.intel.com/en-us/forums/topic/304052" target="_top">Intel
+ <a href="http://software.intel.com/en-us/forums/topic/358472" target="_top">Extended
+ or Quad IEEE FP formats</a> compiler '-Qoption,cpp,--extended_float_type'</a>
+ </li>
</ol></div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/version_id.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/version_id.html 2013-03-25 14:56:11 EDT (Mon, 25 Mar 2013)
@@ -26,7 +26,7 @@
<a name="precision.version_id"></a><a class="link" href="version_id.html" title="Version Info">Version Info</a>
</h2></div></div></div>
<p>
- Last edit to Quickbook file precision.qbk was at 09:47:14 AM on 2013-Mar-25.
+ Last edit to Quickbook file precision.qbk was at 06:50:55 PM on 2013-Mar-25.
</p>
<div class="tip"><table border="0" summary="Tip">
<tr>
==============================================================================
Binary files. No diff available.
==============================================================================
--- sandbox/precision/libs/precision/doc/precision.qbk (original)
+++ sandbox/precision/libs/precision/doc/precision.qbk 2013-03-25 14:56:11 EDT (Mon, 25 Mar 2013)
@@ -558,6 +558,8 @@
# [@ http://gcc.gnu.org/wiki/x87note X8087 notes]
+# [@http://software.intel.com/en-us/forums/topic/304052 Intel __Quad compiler '-Qoption,cpp,--extended_float_type']
+
[endsect] [/section:references References]
[section:version_id Version Info]
==============================================================================
Binary files. No diff available.