summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDebbie Wiles <debs@dwiles.demon.co.uk>2002-05-22 20:44:11 +0000
committerDebbie Wiles <debs@dwiles.demon.co.uk>2002-05-22 20:44:11 +0000
commitf1bbcf31600a0a691f9454803985a45eb4d4fd25 (patch)
tree1924c282b095a9f0807a769d35714fa22d467a59 /doc
parent769f2cf7921c9b2c5284bf30b6753be1a8f49302 (diff)
downloadnasm-f1bbcf31600a0a691f9454803985a45eb4d4fd25.tar.gz
nasm-f1bbcf31600a0a691f9454803985a45eb4d4fd25.tar.bz2
nasm-f1bbcf31600a0a691f9454803985a45eb4d4fd25.zip
Another change to the STRICT documentation
Diffstat (limited to 'doc')
-rw-r--r--doc/nasmdoc.src11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index 6fb734b..3a0a2f1 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -1483,11 +1483,12 @@ invent one using the macro processor.
\H{strict} \i\c{STRICT}: Inhibiting Optimization
When assembling with the optimizer set to level 2 or higher (see
-\k{opt-On}), NASM will override size specifiers (\c{BYTE}, \c{WORD},
-\c{DWORD}, \c{QWORD}, or \c{TWORD}), giving them the smallest possible
-size. The keyword \c{STRICT} can be used to inhibit optimization and
-force a particular operand to be emitted in the specified size.
-For example, with the optimizer on, and in \c{BITS 16} mode,
+\k{opt-On}), NASM will usee size specifiers (\c{BYTE}, \c{WORD},
+\c{DWORD}, \c{QWORD}, or \c{TWORD}), but will give them the smallest
+possible size. The keyword \c{STRICT} can be used to inhibit
+optimization and force a particular operand to be emitted in the
+specified size. For example, with the optimizer on, and in
+\c{BITS 16} mode,
\c push dword 33