IA-32 Intel® Architecture Optimization
2-104
Assembly/Compiler Coding Rule 34. (M impact, M generality) Use
fxch
only where necessary to increase the effective name space. 2-68
Assembly/Compiler Coding Rule 36. (M impact, L generality) Try to
use 32-bit operands rather than 16-bit operands for
fild.
However, do
not do so at the expense of introducing a store forwarding problem by
writing the two halves of the 32-bit memory operand separately. 2-71
Assembly/Compiler Coding Rule 38. (M impact, L generality) Avoid
prefixes, especially multiple non-0F-prefixed opcodes. 2-72
Assembly/Compiler Coding Rule 39. (M impact, L generality) Do not
use many segment registers. 2-72
Assembly/Compiler Coding Rule 40. (ML impact, M generality)
Avoid using complex instructions (for example,
enter
,
leave
, or
loop
)
that generally have more than four µops and require multiple cycles to
decode. Use sequences of simple instructions instead. 2-72
Assembly/Compiler Coding Rule 41. (ML impact, M generality) If a
lea
instruction using the scaled index is on the critical path, a sequence
with
add
s may be better. If code density and bandwidth out of the trace
cache are the critical factor, then use the
lea
instruction. 2-73
Summary of Contents for ARCHITECTURE IA-32
Page 1: ...IA 32 Intel Architecture Optimization Reference Manual Order Number 248966 013US April 2006...
Page 220: ...IA 32 Intel Architecture Optimization 3 40...
Page 434: ...IA 32 Intel Architecture Optimization 9 20...
Page 514: ...IA 32 Intel Architecture Optimization B 60...
Page 536: ...IA 32 Intel Architecture Optimization C 22...