You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain x86-64 instructions assume an operand or memory address size of 64bits, however sometimes a 32bit value is permitted for backwards compatibility. Thus a 0x66 or 0x67 byte is added before the REX prefix or opcode to indicate a 32bit value is used instead of the default 64bit value.
postmodern
changed the title
Add support for adding legacy prefixes (0x66, 0x67) in Ronin::ASM::X86_64::Encoder
Add support for adding x86-64 legacy prefixes (0x66, 0x67) in Ronin::ASM::X86_64::EncoderMar 8, 2025
Certain x86-64 instructions assume an operand or memory address size of 64bits, however sometimes a 32bit value is permitted for backwards compatibility. Thus a
0x66
or0x67
byte is added before the REX prefix or opcode to indicate a 32bit value is used instead of the default 64bit value.Examples
References
The text was updated successfully, but these errors were encountered: