ModR/M Historical Notation /0.../7
While learning about x64, I struggled to understand some notations in the intel manual.
Let's look at 0xC7 MOV:
| opcode | instruction | Op/Enc | Description |
|---|---|---|---|
| C7 /0 iw | MOV r/m16, imm16 | MI | Move imm16 to r/m16. |
| C7 /0 id | MOV r/m32, imm32 | MI | Move imm32 to r/m32. |
| REX.W + C7 /0 id | MOV r/m64, imm32 | MI | Move imm32 sign extended to 64-bits to r/m64. |
About the /0../7 it says:
Historically this document only specified the ModR/M.reg field restrictions with the notation /0 ... /7 and did not specify restrictions on the ModR/M.mod and ModR/M.r/m fields in the encoding boxes.
My questions are:
- That number after
/0is a restriction code, but which restriction? What does it mean while interpreting an instruction? - If I'm reading bytes like
c7c701020304...How to know if I need to ready imm16(0102or imm32(01020304)? By testing, I know that in thisimm32, but I don't understand why. I deduce that it is related to rex+modrm.
{ xxd --ps -r | ndisasm -b64 -; } <<<c7c701020304
00000000 C7C701020304 mov edi,0x4030201
- In other words: Why
ndisasmparses that asimm32insteadimm16?
/digit still only restricts the ModRM.reg field. It means, put whatever digit is after the slash, in the reg field of the ModRM byte.
That note is about new Intel AMX instructions, some of which have a different ModRM specification. For example TDPBSSD/TDPBSUD/TDPBUSD/TDPBUU require mod=11 (in other words, they cannot have a memory operand)
And TILELOADD/TILELOADDT1 require mod!=11 and rm=100 (they must have a memory operand, and it must be encoded with SIB)
- Push and Pop on AMD64
- Number of memory accesses
- Can gcc compile x86 assembly or just link it?
- How to populate a 64-bit register with duplicate byte values?
- Address size on PlayStation 3/PowerPC
- Why does a std::atomic store with sequential consistency use XCHG?
- x86 MUL Instruction from VS 2008/2010
- LDAXRB and STXRB instructions - what is the "exclusive access to the memory address" in ARM64?
- How to use shifter operands in GNU arm assembly syntax?
- QtSPIM: Explanation for code shown without loading program
- In ARM Cortex, the stack pointer increases instead of decreasing when allocating space for a local variable
- What are the best instruction sequences to generate vector constants on the fly?
- Replace digit with a word and write to a file using assembler 8086
- Angr unconstrained state has the same address as a found state
- What would happen if the CS segment register is changed? (And how would you do so?)
- Why are we switching segments while calculating string length?
- How to fix: (cannot have implicit far jump or call to near label) and (use a register assumed to ERROR)
- Is this inline asm correct for bitcasting int as float?
- Run a given program by user
- Assembly x86 to C
- gcc command for keeping addresses as they were?
- Tool to Debug Guest OS in Virtual Box
- Disassembly view of C# 64-bit Release code is 75% longer than 32-bit Debug code?
- Programming arrays in LMC
- Why modern calling conventions pass variadic arguments in registers?
- cross compile (arm-none-eabi-as) arm assembly error "junk at end of line /" or undefined symbol
- Understanding Memory Controller RPQ/WPQ ordering guarantees for loads and ntstores
- How to sum up all ascii values of elements in a stack in assembly x86
- INC instruction vs ADD 1: Does it matter?
- Issue with DWARF DIE's and tracking variables