Boost-Commit mailing page: [Boost-commit] svn:boost r84008 - in sandbox/precision/libs/precision/doc: . html html/precision

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r84008 - in sandbox/precision/libs/precision/doc: . html html/precision
From: pbristow_at_[hidden]
Date: 2013-04-22 12:01:09

Author: pbristow
Date: 2013-04-22 12:01:06 EDT (Mon, 22 Apr 2013)
New Revision: 84008
URL: http://svn.boost.org/trac/boost/changeset/84008

Log:
Further minor corrections - standard text is added by reference to a separate file
Binary files modified:
   sandbox/precision/libs/precision/doc/precision.pdf
Text files modified:
   sandbox/precision/libs/precision/doc/html/index.html | 5
   sandbox/precision/libs/precision/doc/html/precision/literals.html | 6
   sandbox/precision/libs/precision/doc/html/precision/thestandard.html | 144 ---------------------------------------
   sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html | 4
   sandbox/precision/libs/precision/doc/html/precision/version_id.html | 2
   sandbox/precision/libs/precision/doc/n3626 | 2
   sandbox/precision/libs/precision/doc/precision.qbk | 110 ++----------------------------
   7 files changed, 20 insertions(+), 253 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-04-22 12:01:06 EDT (Mon, 22 Apr 2013)
@@ -71,14 +71,15 @@
 ISO/IEC JTC1 SC22 WG14/ Numerics N1703 - 2013-04-18
 

- Revised after WG21/SG6 meeting 18 Apr 2013.
+ Revised after WG21/SG6 meeting 18 Apr 2013, and 22 Apr 2013 adding a reference
+ to standard text in raw html.
 

 Comments and suggestions to Paul.A.Bristow pbristow_at_hetp.u-net.com.
 
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left">Last revised: April 19, 2013 at 13:30:19 GMT</td>
+<td align="left">Last revised: April 22, 2013 at 16:00:41 GMT</td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>

Modified: sandbox/precision/libs/precision/doc/html/precision/literals.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/literals.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/literals.html 2013-04-22 12:01:06 EDT (Mon, 22 Apr 2013)
@@ -37,7 +37,7 @@
 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 80 128 256 512 MAX}_C
+<pre class="programlisting">FLOAT{16 32 64 80 128 MAX}_C
</pre>

 The code below, for example, initializes a constant <code class="computeroutput">float128_t</code>
@@ -59,8 +59,8 @@
 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 80 128 256 512}_MIN
-FLOAT_[FAST LEAST]{16 32 64 80 128 256 512}_MAX
+<pre class="programlisting">FLOAT_[FAST LEAST]{16 32 64 80 128}_MIN
+FLOAT_[FAST LEAST]{16 32 64 80 128}_MAX
FLOATMAX_MIN
FLOATMAX_MAX
</pre>

Modified: sandbox/precision/libs/precision/doc/html/precision/thestandard.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/thestandard.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/thestandard.html 2013-04-22 12:01:06 EDT (Mon, 22 Apr 2013)
@@ -73,149 +73,9 @@
 18.11 Floating-Point Types having Specified Widths
 

- 18.11.1 Header <cstdfloat> synopsis [cstdfloat.syn]
+ <a href="https://svn.boost.org/svn/boost/sandbox/precision/libs/precision/doc/n3626%20standard.html" target="_top">n3626
+ standard text</a>
 
-
- Header <code class="computeroutput">cstdfloat.h</code>
- 
-
- All implementations should define this header, even if none of the <code class="computeroutput">typedef</code>s are available, when it will be an empty
- file.
- 
-
- Only those <code class="computeroutput">typedef</code>s that are appropriate
- should be defined. For example, if a <code class="computeroutput">double</code>
- type is not in IEEE754 format, then <code class="computeroutput">typedef
- floating-point-type
- float64_t</code> should not
- be defined. This will ensure that programs that try to use a <code class="computeroutput">typedef</code> that is not defined on that platform
- will simply fail to compile.
- 
-
- <code class="computeroutput">typedef</code>s of the format <code class="computeroutput">floatN_t</code> are for IEE754 types (were available)
- providing exactly N bits. For these types that are defined, <code class="computeroutput">std::numeric_limits<T>::is_iec559 == true</code>.
- 
-
- <code class="computeroutput">typedef</code>s of the format <code class="computeroutput">float_leastN_t</code> provide types with at least
- the precision N, but do not specify the layout.
- 
-
- <code class="computeroutput">typedef</code>s of the format <code class="computeroutput">float_fastN_t</code> provide types with at least
- the precision N, and provide the fastest execution, and do not
- specify the layout.
- 
-
- The use of denormals is implementation dependent, but can be determined for
- any type T from <code class="computeroutput">std::numeric_limits<T>::has_denorm, denorm_min</code>
- and <code class="computeroutput">float_denorm_style</code>.
- 
-
- The endianness of the layout of the floating-point types is not specified here
- (though it may be possible to determine this - see note 9).
- 
-<pre class="programlisting">namespace std
-{
- typedef floating-point type float8_t; // optional (See note 1).
- typedef floating-point type float16_t; // optional (See note 2).
- typedef floating-point type float24_t; // optional (See note 3.
- typedef floating-point type float32_t; // optional (See note 4).
- typedef floating-point type float64_t; // optional (See note 5).
- typedef floating-point type float80_t; // optional (See note 6).
- typedef floating-point type float128_t; // optional (See note 7).
- typedef floating-point type floatmax_t; // optional (largest floating-point type available).
-
- 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_least128_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.
-}
-</pre>
-
- Notes
- 
-
- 1 There is no IEEE754/IEC559 specification for a 8-bit floating-point type,
- so the layout is implementation dependent. The type should occupy exactly 8
- bits to allow optimisation.
- 
-
- 2 There is no IEEE754/IEC559 specification for a 24-bit floating-point type,
- so the layout is implementation dependent.
- 
-
- 3 IEEE754 Half precision.
- 
-
- 4 IEEE754 Single precision.
- 
-
- 5 IEEE754 Double precision.
- 
-
- 6 IEEE754 Extended precision. This type may be implemented using 128 bits,
- with padding. The size and location of any padding is implementation dependent,
- so this type is unlikely to be suitable for binary interchange.
- 
-
- 7 IEEE754 Quadruple precision.
- 
-
- 8 The use of denormals is implementation dependent, but can be determined for
- any type T from <code class="computeroutput">std::numeric_limits<T>::has_denorm, denorm_min</code>
- and <code class="computeroutput">float_denorm_style</code>.
- 
-
- 9 If cooperating programs wish to try to use binary interchange for IEEE754/IEC559
- types of <code class="computeroutput">float_N_t</code>, for example
- for serialization, because the endianness of the layout of the floating-point
- types is not specified (but may be determined) therefore programs must ensure
- that they all use the same endianness and the same use of denormals.
- 
-
- The header <code class="computeroutput">stdfloat.h</code> (called by <code class="computeroutput"><cstdfloat></code>
- should also contain all necessary C function macros in the form shown below.
- 
-<pre class="programlisting">FLOAT{16 32 64 80 128 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.h` or `#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">const 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 80 128}_MIN
-FLOAT_[FAST LEAST]{16 32 64 80 128}_MAX
-FLOATMAX_MIN
-FLOATMAX_MAX
-</pre>
-
- These macros can be used to query the ranges of the optional floating-point
- typedefs having specified widths at compile-time. For example,
- 
-<pre class="programlisting">#include <limits>
-#include <cstdfloat>
-
-static_assert(FLOATMAX_MAX > (std::numeric_limits<float>::max)(),
- "The iec559 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>

Modified: sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/thetypedefs.html 2013-04-22 12:01:06 EDT (Mon, 22 Apr 2013)
@@ -80,8 +80,8 @@

 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
+ and <code class="computeroutput">float128_t</code> will probably
+ behave identically when used on any platform with any implementation that correctly
 supports the <code class="computeroutput">typedef</code>s.

Modified: sandbox/precision/libs/precision/doc/html/precision/version_id.html
==============================================================================
--- sandbox/precision/libs/precision/doc/html/precision/version_id.html (original)
+++ sandbox/precision/libs/precision/doc/html/precision/version_id.html 2013-04-22 12:01:06 EDT (Mon, 22 Apr 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>

- Last edit to Quickbook file precision.qbk was at 02:30:19 PM on 2013-Apr-19.
+ Last edit to Quickbook file precision.qbk was at 05:00:41 PM on 2013-Apr-22.

<div class="tip"><table border="0" summary="Tip">
<tr>

Modified: sandbox/precision/libs/precision/doc/n3626 standard.html
==============================================================================
--- sandbox/precision/libs/precision/doc/n3626 standard.html (original)
+++ sandbox/precision/libs/precision/doc/n3626 standard.html 2013-04-22 12:01:06 EDT (Mon, 22 Apr 2013)
@@ -1,4 +1,4 @@
-<HTML><HEAD><TITLE>N3626, Proposal for Unbounded-Precision Integer Types</TITLE></HEAD><BODY>
+<HTML><HEAD><TITLE>N3626, Proposal for floating-point-typedefs Having Specified Widths</TITLE></HEAD><BODY>

<CENTER>
<H1><A NAME="N3626, Proposal for floating-point-typedefs Having Specified Widths">Proposal for floating-point-typedefs Having Specified Widths</A></H1>

Modified: sandbox/precision/libs/precision/doc/precision.pdf
==============================================================================
Binary files. No diff available.

Modified: sandbox/precision/libs/precision/doc/precision.qbk
==============================================================================
--- sandbox/precision/libs/precision/doc/precision.qbk (original)
+++ sandbox/precision/libs/precision/doc/precision.qbk 2013-04-22 12:01:06 EDT (Mon, 22 Apr 2013)
@@ -17,7 +17,7 @@

ISO/IEC JTC1 SC22 WG14/ Numerics N1703 - 2013-04-18

-Revised after WG21/SG6 meeting 18 Apr 2013.
+Revised after WG21/SG6 meeting 18 Apr 2013, and 22 Apr 2013 adding a reference to standard text in raw html.

Comments and suggestions to Paul.A.Bristow pbristow_at_hetp.u-net.com.

@@ -180,7 +180,7 @@

It means that floating-point software written with
`float16_t`, `float32_t`, `float64_t`, and `float128_t`
-should behave identically when used on any platform
+will probably behave identically when used on any platform
with any implementation that correctly supports the `typedef`s.

It also creates the opportunity to implement quadruple-precision (__IEEE_Quad)
@@ -192,7 +192,8 @@
* `float11_t, float24_t, float53_t, float113_t, ...`
* `float16_t, float32_t, float64_t, float128_t, ...`

-The first set above is intuitively coined from [@http://dx.doi.org/10.1109/IEEESTD.2008.4610935 IEE754:2008].
+The first set above is intuitively coined from
+[@http://dx.doi.org/10.1109/IEEESTD.2008.4610935 IEE754:2008].
It is also consistent with the gist of integer types having specified widths
such as `int64_t`, in so far as the number of binary digits of ['significand] precision
is contained within the name of the data type.
@@ -319,7 +320,7 @@
The header `<cstdfloat>` should contain all necessary
C-style function macros in the form shown below.

- FLOAT{16 32 64 80 128 256 512 MAX}_C
+ FLOAT{16 32 64 80 128 MAX}_C

The code below, for example, initializes a constant `float128_t`
value using one of these macros.
@@ -338,8 +339,8 @@
In addition, the header `<cstdfloat>` should contain all
necessary macros of the form:

- FLOAT_[FAST LEAST]{16 32 64 80 128 256 512}_MIN
- FLOAT_[FAST LEAST]{16 32 64 80 128 256 512}_MAX
+ FLOAT_[FAST LEAST]{16 32 64 80 128}_MIN
+ FLOAT_[FAST LEAST]{16 32 64 80 128}_MAX
FLOATMAX_MIN
FLOATMAX_MAX

@@ -395,102 +396,7 @@

18.11 Floating-Point Types having Specified Widths

-18.11.1 Header <cstdfloat> synopsis [cstdfloat.syn]
-
-Header `cstdfloat.h`
-
-All implementations should define this header, even if none of the `typedef`s are available, when it will be an empty file.
-
-Only those `typedef`s that are appropriate should be defined. For example, if a `double` type is not in IEEE754 format,
-then `typedef floating-point-type float64_t` should *not* be defined.
-This will ensure that programs that try to use a `typedef` that is not defined on that platform will simply fail to compile.
-
-`typedef`s of the format `floatN_t` are for IEE754 types (were available) providing exactly N bits.
-For these types that are defined, `std::numeric_limits<T>::is_iec559 == true`.
-
-`typedef`s of the format `float_leastN_t` provide types with at least the precision N, but do *not* specify the layout.
-
-`typedef`s of the format `float_fastN_t` provide types with at least the precision N, and provide the fastest execution, and do *not* specify the layout.
-
-The use of denormals is implementation dependent, but can be determined for any type T from `std::numeric_limits<T>::has_denorm, denorm_min` and `float_denorm_style`.
-
-The endianness of the layout of the floating-point types is not specified here (though it may be possible to determine this - see note 9).
-
- namespace std
- {
- typedef floating-point type float8_t; // optional (See note 1).
- typedef floating-point type float16_t; // optional (See note 2).
- typedef floating-point type float24_t; // optional (See note 3.
- typedef floating-point type float32_t; // optional (See note 4).
- typedef floating-point type float64_t; // optional (See note 5).
- typedef floating-point type float80_t; // optional (See note 6).
- typedef floating-point type float128_t; // optional (See note 7).
- typedef floating-point type floatmax_t; // optional (largest floating-point type available).
-
- 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_least128_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.
- }
-
-Notes
-
-1 There is no IEEE754/IEC559 specification for a 8-bit floating-point type, so the layout is implementation dependent. The type should occupy exactly 8 bits to allow optimisation.
-
-2 There is no IEEE754/IEC559 specification for a 24-bit floating-point type, so the layout is implementation dependent.
-
-3 IEEE754 Half precision.
-
-4 IEEE754 Single precision.
-
-5 IEEE754 Double precision.
-
-6 IEEE754 Extended precision. This type may be implemented using 128 bits, with padding.
-The size and location of any padding is implementation dependent, so this type is unlikely to be suitable for binary interchange.
-
-7 IEEE754 Quadruple precision.
-
-8 The use of denormals is implementation dependent, but can be determined for any type T from `std::numeric_limits<T>::has_denorm, denorm_min` and `float_denorm_style`.
-
-9 If cooperating programs wish to try to use binary interchange for IEEE754/IEC559 types of `float_N_t`,
-for example for serialization,
-because the endianness of the layout of the floating-point types is not specified (but may be determined)
-therefore programs must ensure that they all use the same endianness and the same use of denormals.
-
-The header `stdfloat.h` (called by `<cstdfloat>` should also contain all necessary C function macros in the form shown below.
-
- FLOAT{16 32 64 80 128 MAX}_C
-
-The code below, for example, initializes a constant `float128_t` value using one of these macros.
-
- `#include cstdfloat.h` or `#include <cstdfloat>`
-
- constexpr std::float128_t euler = FLOAT128_C(0.57721566490153286060651209008240243104216);
-
-The following code initializes a constant `float16_t` value using another one of these macros.
-
- const std::float16_t euler = FLOAT16_C(0.577216);
-
-In addition, the header `<cstdfloat>` should contain all necessary macros of the form:
-
- FLOAT_[FAST LEAST]{16 32 64 80 128}_MIN
- FLOAT_[FAST LEAST]{16 32 64 80 128}_MAX
- FLOATMAX_MIN
- FLOATMAX_MAX
-
-These macros can be used to query the ranges of the optional floating-point typedefs having specified widths at compile-time. For example,
-
- #include <limits>
- #include <cstdfloat>
-
- static_assert(FLOATMAX_MAX > (std::numeric_limits<float>::max)(),
- "The iec559 floating-point range is too small.");
+[@https://svn.boost.org/svn/boost/sandbox/precision/libs/precision/doc/n3626%20standard.html n3626 standard text]

[endsect] [/section:thestandard Place in the standard]

Date view	Thread view	Subject view	Author view