|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r83674 - sandbox/precision/libs/precision/doc
From: e_float_at_[hidden]
Date: 2013-04-01 08:47:28
Author: christopher_kormanyos
Date: 2013-04-01 08:47:27 EDT (Mon, 01 Apr 2013)
New Revision: 83674
URL: http://svn.boost.org/trac/boost/changeset/83674
Log:
Clarification of Intel's _Quad internal data type.
Text files modified:
sandbox/precision/libs/precision/doc/precision.qbk | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
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-01 08:47:27 EDT (Mon, 01 Apr 2013)
@@ -534,7 +534,8 @@
# [@http://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html GNU C supports additional floating types, `__float80` and `__float128` to support 80-bit (XFmode) and 128-bit (TFmode) floating types.]
-# __Quad by Intel Intel64 mode on Linux (V12.1) provides 128 bit `long double` 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.
+# Intel provides an internal 128-bit floating-point type. When the `-Qoption,cpp,--extended_float_type` command line option is supplied, it supports what appears to be an undocumented data type `_Quad`. This type is equivalent to GCC's `__float128`.
+
# [@http://software.intel.com/en-us/forums/topic/358476 Intel FORTRAN REAL*16] 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.
# The 360/85 and follow-on System/370 added support for a 128-bit "extended" __IBM_hexadecimal. These formats are still supported in the current design, where they are now called the "hexadecimal floating point" (HFP) formats.
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