aboutsummaryrefslogtreecommitdiffstats
path: root/doc/Makefile.in
diff options
context:
space:
mode:
authorCyrill Gorcunov <gorcunov@gmail.com>2010-06-25 15:45:19 +0400
committerCyrill Gorcunov <gorcunov@gmail.com>2010-06-25 18:28:15 +0400
commitf85cd55731bd4be6638a37855c41b9c93d858f91 (patch)
tree0624b50147a80821e01c3c03c97b6bbbf123966b /doc/Makefile.in
parentefb358339d92548d97022585ee7f09eb29b95a88 (diff)
downloadnasm-daily-f85cd55731bd4be6638a37855c41b9c93d858f91.tar.gz
nasm-daily-f85cd55731bd4be6638a37855c41b9c93d858f91.tar.xz
nasm-daily-f85cd55731bd4be6638a37855c41b9c93d858f91.zip
BR 3020760: insns.dat -- confirm push imm32 on x86-64 explicitlynasm-2.09rc1-20100625
PUSH imm64 confuses ones who is trying to find this instruction in processor programming manuals. Actually it was introduced in a sake of "push `size' imm" consistency. In other words -- to allow users to state "PUSH qword imm32" in 64bit code, though on byte level (ie generated) code it still has a correct and valid sign-extended "PUSH imm32" instruction. To get rid of this ambiguie bite we make explicit "PUSH imm32" being valid in 64bit code. This also makes "PUSH dword imm32" valid in 64bit code as well. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
Diffstat (limited to 'doc/Makefile.in')
0 files changed, 0 insertions, 0 deletions