aniani/nasm
0
0
Fork 1
mirror of https://github.com/netwide-assembler/nasm.git synced 2025-07-24 10:25:42 -04:00
Code

Updated documentation for the STRICT keyword.

Browse Source
This commit is contained in:
Debbie Wiles 2002-05-22 20:14:52 +00:00
parent 8311d9f310
commit 9642d4fd7f
1 changed files with 11 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/nasmdoc.src
View File

@ -701,7 +701,8 @@ The syntax is:
are optimised, unless the long form is specified. are optimised, unless the long form is specified.
\b \c{-On} multi-pass optimization, minimize branch offsets; also will \b \c{-On} multi-pass optimization, minimize branch offsets; also will
minimize signed immediate bytes, overriding size specification. minimize signed immediate bytes, overriding size specification
when the \c{strict} keyword hasn't been used (see \k{strict}).
If 2 <= n <= 3, then there are 5 * n passes, otherwise there If 2 <= n <= 3, then there are 5 * n passes, otherwise there
are n passes. are n passes.
@ -1481,13 +1482,12 @@ invent one using the macro processor.
\H{strict} \i\c{STRICT}: Inhibiting Optimization \H{strict} \i\c{STRICT}: Inhibiting Optimization
When compiling with the optimizer set to level 2 or higher (see When assembling with the optimizer set to level 2 or higher (see
\k{opt-On}), NASM will use size specifiers (\c{BYTE}, \c{WORD}, \k{opt-On}), NASM will override size specifiers (\c{BYTE}, \c{WORD},
\c{DWORD}, \c{QWORD}, or \c{TWORD}) strictly to choose the address- or \c{DWORD}, \c{QWORD}, or \c{TWORD}), giving them the smallest possible
operand-size of the instruction. The keyword \c{STRICT} can be used size. The keyword \c{STRICT} can be used to inhibit optimization and
to inhibit optimization and force a particular operand to be emitted force a particular operand to be emitted in the specified size.
in the specified size. For example, with the optimizer on, and in For example, with the optimizer on, and in \c{BITS 16} mode,
\c{BITS 16} mode,
\c push dword 33 \c push dword 33
@ -1498,6 +1498,9 @@ is encoded in three bytes \c{66 6A 21}, whereas
is encoded in six bytes, with a full dword immediate operand \c{66 68 is encoded in six bytes, with a full dword immediate operand \c{66 68
21 00 00 00}. 21 00 00 00}.
With the optimizer off, the same code (six bytes) is generated whether
the \c{STRICT} keyword was used or not.
\H{crit} \i{Critical Expressions} \H{crit} \i{Critical Expressions}