VPROTB instruction (XOP)

Forms

Every encoding of VPROTB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.

Instruction	Encoding	Requires
`VPROTB xmm, m128, imm8` VPROTB_XMMdq_MEMdq_IMMb	`XOP.128.NP.08.W0 C0 /r ib`	XOP
`VPROTB xmm, xmm, imm8` VPROTB_XMMdq_XMMdq_IMMb	`XOP.128.NP.08.W0 C0 /r ib`	XOP
`VPROTB xmm, m128, xmm` VPROTB_XMMdq_MEMdq_XMMdq	`XOP.128.NP.09.W0 90 /r`	XOP
`VPROTB xmm, xmm, xmm` VPROTB_XMMdq_XMMdq_XMMdq	`XOP.128.NP.09.W0 90 /r` `XOP.128.NP.09.W1 90 /r`	XOP
`VPROTB xmm, xmm, m128` VPROTB_XMMdq_XMMdq_MEMdq	`XOP.128.NP.09.W1 90 /r`	XOP

Data flow

Where the elements of the sources go, element 0 on the right; results that depend on a control value are drawn for an example. How to read.

Element-wise: each byte of the result comes from the byte in the same place in each source.VPROTB xmm, xmm/m128, imm8

Shown: bytes 7 to 0. Every byte works alike: 16 bytes in the xmm form.

Result byte i comes from byte i of xmm2. Result bytes 7 to 0: r7, r6, r5, r4, r3, r2, r1, r0.

Element-wise: each byte of the result comes from the byte in the same place in each source.VPROTB xmm, xmm/m128, xmm VPROTB xmm, xmm, m128

Shown: bytes 7 to 0. Every byte works alike: 16 bytes in the xmm form.

Result byte i comes from byte i of xmm2 and xmm3. Result bytes 7 to 0: r7, r6, r5, r4, r3, r2, r1, r0.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

VPROTB xmm, xmm/m128, imm8

features = cpuid_leaf(0x80000001, 0)[2]
if not features >> 11 & 1:
    fault(UD)  # CPUID: no XOP
for i in range(16):
    xmm1.b[i] = rol(src2.b[i], imm8, 8)
# a negative count rotates right
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 2 cases. Its cases ran where CPUID reported no XOP, and every one raised an exception.

VPROTB xmm, xmm/m128, xmm VPROTB xmm, xmm, m128

features = cpuid_leaf(0x80000001, 0)[2]
if not features >> 11 & 1:
    fault(UD)  # CPUID: no XOP
for i in range(16):
    xmm1.b[i] = rol(src2.b[i], src3.b[i], 8)
# a negative count rotates right
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 3 cases. Its cases ran where CPUID reported no XOP, and every one raised an exception.

Operands

What each form reads and writes, as Intel XED records it: the operands of its syntax, in order, and the implicit ones that the syntax does not name. How to read.

Operand	Kind	Action
`VPROTB xmm, xmm/m128, imm8`
`xmm`	explicit	write
`xmm/m128`	explicit	read
`imm8`	explicit	read
`VPROTB xmm, xmm/m128, xmm`
`xmm`	explicit	write
`xmm/m128`	explicit	read
`xmm`	explicit	read
`VPROTB xmm, xmm, m128`
`xmm`	explicit	write
`xmm`	explicit	read
`m128`	explicit	read

Flags

None: XED records no flag that the forms test or change.

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPROTB, each with the form it compiles to and the Clang options it needs. The forms come from compiling every intrinsic and decoding the result with Intel XED; all intrinsics A–Z explains the method.

Intrinsic	Compiles to
`_mm_rot_epi8` `__m128i _mm_rot_epi8(__m128i __A, __m128i __B)`	`VPROTB xmm, xmm, xmm` XOP.128 -mxop
`_mm_roti_epi8` `__m128i _mm_roti_epi8(__m128i A, const int N)`	`VPROTB xmm, xmm, imm8` XOP.128 -mxop

CPUID and processors

Each form belongs to an XED ISA set. A form can be used when the processor reports every CPUID bit of one of its ISA set's alternatives.

CPUID requirements and processors of the XED ISA sets above. Alternatives are separated by “or”; processors follow XED’s chip model, whose AMD processors end with Zen 2, and the CPU data of this site for Zen 3 to Zen 6.

ISA set	CPUID	Processors
`XOP` XOP	XOP `CPUID.80000001H:ECX[11]` XOP	Bulldozer, Piledriver

More XOP instructions

All 55 XOP instructions