aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@linux.intel.com>2010-05-07 13:21:20 -0700
committerH. Peter Anvin <hpa@linux.intel.com>2010-05-07 13:21:20 -0700
commit19cbe0c1c4da84cab01bf58de16621ecca46bd58 (patch)
treedbbf95a44dc052e768c43fb049bc23b0a111c3b9
parentc8d8a13cde4de4275703dba0116567820ebaf2b1 (diff)
downloadnasm-test-19cbe0c1c4da84cab01bf58de16621ecca46bd58.tar.gz
nasm-test-19cbe0c1c4da84cab01bf58de16621ecca46bd58.tar.xz
nasm-test-19cbe0c1c4da84cab01bf58de16621ecca46bd58.zip
nasmdoc: document octal/binary floating-point
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
-rw-r--r--doc/nasmdoc.src14
1 files changed, 9 insertions, 5 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index b77fa674..8b6fb2dc 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -1619,11 +1619,15 @@ Floating-point constants are expressed in the traditional form:
digits, then a period, then optionally more digits, then optionally an
\c{E} followed by an exponent. The period is mandatory, so that NASM
can distinguish between \c{dd 1}, which declares an integer constant,
-and \c{dd 1.0} which declares a floating-point constant. NASM also
-support C99-style hexadecimal floating-point: \c{0x}, hexadecimal
-digits, period, optionally more hexadeximal digits, then optionally a
-\c{P} followed by a \e{binary} (not hexadecimal) exponent in decimal
-notation.
+and \c{dd 1.0} which declares a floating-point constant.
+
+NASM also support C99-style hexadecimal floating-point: \c{0x},
+hexadecimal digits, period, optionally more hexadeximal digits, then
+optionally a \c{P} followed by a \e{binary} (not hexadecimal) exponent
+in decimal notation. As an extension, NASM additionally supports the
+\c{0h} and \c{$} prefixes for hexadecimal, as well binary and octal
+floating-point, using the \c{0b} or \c{0y} and \c{0o} or \c{0q}
+prefixes, respectively.
Underscores to break up groups of digits are permitted in
floating-point constants as well.