| commit | f85cd55731bd4be6638a37855c41b9c93d858f91 | |
| author | Cyrill Gorcunov <gorcunov@gmail.com> | |
| Fri, 25 Jun 2010 11:45:19 +0000 (25 15:45 +0400) | ||
| committer | Cyrill Gorcunov <gorcunov@gmail.com> | |
| Fri, 25 Jun 2010 14:28:15 +0000 (25 18:28 +0400) | ||
| tree | 0624b50147a80821e01c3c03c97b6bbbf123966b | treesnapshot (tar.gz zip) |
| parent | efb358339d92548d97022585ee7f09eb29b95a88 | commitdiff |
BR 3020760: insns.dat -- confirm push imm32 on x86-64 explicitly
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>
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>
| insns.dat | diffblobblamehistory |