From f1bbcf31600a0a691f9454803985a45eb4d4fd25 Mon Sep 17 00:00:00 2001 From: Debbie Wiles Date: Wed, 22 May 2002 20:44:11 +0000 Subject: [PATCH] Another change to the STRICT documentation --- doc/nasmdoc.src | 11 ++++++----- 1 file 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 -- 2.7.4