aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@zytor.com>2018-11-28 09:50:14 -0800
committerH. Peter Anvin <hpa@zytor.com>2018-11-28 09:50:14 -0800
commitc06c87dbb5358b99968fe2348957fca92ae2ef30 (patch)
tree6c938cc810a0678b5a9e3fb2b946d25f093fa692
parentee75ec2eed7053144481deefa10cb543dbfbd9bc (diff)
downloadnasm-c06c87dbb5358b99968fe2348957fca92ae2ef30.tar.gz
nasm-c06c87dbb5358b99968fe2348957fca92ae2ef30.tar.xz
nasm-c06c87dbb5358b99968fe2348957fca92ae2ef30.zip
changes.src: fp bug: there are probably other corner cases
There are probably other corner cases where we could at the very least produce an incorrectly rounded result, so be a bit more cagey about the description of the bug. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
-rw-r--r--doc/changes.src7
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/changes.src b/doc/changes.src
index eab31a9c..ffbcda0d 100644
--- a/doc/changes.src
+++ b/doc/changes.src
@@ -21,10 +21,9 @@ operator refers to an \c{EXTERN} symbol declared further down in the
code.
\b Fix a corner case in the floating-point code where a binary, octal
-or hexadecimal floating-point constant starting with digits 1, 1-3, or
-8-F, respectively, and having at least 32, 11, or 8 mantissa digits,
-could produce incorrect results for the 80-bit and 128-bit
-floating-point formats.
+or hexadecimal floating-point having at least 32, 11, or 8 mantissa
+digits could produce slightly incorrect results under very specific
+conditions.
\S{cl-2.14} Version 2.14