[PATCH] x86/Intel: fix indirect far jmp/call with operand size specified
Jan Beulich
jbeulich@novell.com
Fri Feb 22 15:33:00 GMT 2008
>> -jmp, 1, 0xff, 0x4, 1, Cpu64, Modrm|No_bSuf|No_lSuf|No_sSuf|No_ldSuf|NoRex64, { Reg64|Qword|Unspecified|BaseIndex|Disp8|Disp32|Disp32S|JumpAbsolute }
>> +jmp, 1, 0xff, 0x4, 1, Cpu64, Modrm|No_bSuf|No_lSuf|No_sSuf|No_ldSuf|NoRex64, { Reg16|Reg64|Word|Qword|Unspecified|BaseIndex|Disp8|Disp32|Disp32S|JumpAbsolute }
>
>This is wrong. 64bit jump/call only support 64bit reg/mem.
I just made jmp match call. And I'm pretty sure it's actually valid (despite
being pointless); I think I even tried it out once. It's just like 16-bit
push/pop is encodable, even though it makes little sense.
Jan
More information about the Binutils
mailing list