Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VPROLD rotates each doubleword left by the count in its immediate: the bits that leave at the top come back in at the bottom. It is AVX-512F’s, with masking, a broadcast source and the xmm and ymm forms under AVX512VL; before it, SSE and AVX2 had no vector rotate, and only AMD’s XOP had one, VPROTD. VPRORD rotates right, which is the same as rotating left by 32 minus the count; VPROLVD takes a count per element from a register, and VPROLQ rotates quadwords.

The count

Only the low 5 bits of the immediate count, so a count of 33 rotates by 1 and 32 by nothing. The cases recorded on Zen 5 show this with 21h: 7FFFFFFFh became FFFFFFFEh and 80000000h became 1, as a rotate by one gives. ROL on a 32-bit register masks its count the same way, but there the count can come from CL; here it is fixed in the instruction.

From shifts to one instruction

Without AVX-512, a rotate is two shifts and an OR. For a loop over a uint32_t array computing (x << 7) | (x >> 25), GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 emit VPSLLD, VPSRLD and VPOR, except that Clang turns rotations by 8 and 16, which move whole bytes, into one VPSHUFB. With -march=x86-64-v4 both compilers recognize the pattern and emit VPROLD for every count, on zmm registers in GCC and on ymm in Clang.

Ciphers and hashes built from 32-bit words rotate a lot. Intel’s optimization guide shows SM4 encryption with AVX-512 and GFNI, where each round’s linear step XORs a word with its rotations by 2, 10, 18 and 24, four VPROLDs combined with VPTERNLOGD (Example 19-2).

AMD’s Zen 5 guide lists VPROLD as one macro-op with a latency of two cycles: the same latency as an EVEX shift by an immediate followed by an OR, one cycle each, in one instruction instead of three. The VEX shifts of the -march=x86-64-v3 code take two cycles each.

Forms

Every encoding of VPROLD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPROLD zmm {k}{z}, zmm, imm8 VPROLD_ZMMu32_MASKmskw_ZMMu32_IMM8_AVX512EVEX.512.66.0F.W0 72 /1 ibAVX10.1 or AVX512F
VPROLD zmm {k}{z}, m512/m32bcst, imm8 VPROLD_ZMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.512.66.0F.W0 72 /1 ibAVX10.1 or AVX512F
VPROLD xmm {k}{z}, xmm, imm8 VPROLD_XMMu32_MASKmskw_XMMu32_IMM8_AVX512EVEX.128.66.0F.W0 72 /1 ibAVX10.1 or AVX512F + AVX512VL
VPROLD xmm {k}{z}, m128/m32bcst, imm8 VPROLD_XMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.128.66.0F.W0 72 /1 ibAVX10.1 or AVX512F + AVX512VL
VPROLD ymm {k}{z}, ymm, imm8 VPROLD_YMMu32_MASKmskw_YMMu32_IMM8_AVX512EVEX.256.66.0F.W0 72 /1 ibAVX10.1 or AVX512F + AVX512VL
VPROLD ymm {k}{z}, m256/m32bcst, imm8 VPROLD_YMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.256.66.0F.W0 72 /1 ibAVX10.1 or AVX512F + AVX512VL

Latency and throughput

What the scheduling models of LLVM 23.1.2 give for each form, not measurements: latency / reciprocal throughput in cycles, the ports under them. A row is a model, or models that agree; a dash, a form that its processors lack. Memory forms: latency from the address, ports without the load and store units. Which processors each model covers.
Modelzmm {k}{z}, zmm, imm8zmm {k}{z}, m512/m32bcst, imm8xmm {k}{z}, xmm, imm8
ymm {k}{z}, ymm, imm8
xmm {k}{z}, m128/m32bcst, imm8ymm {k}{z}, m256/m32bcst, imm8
Skylake-SP, Ice Lake1 / 1p08 / 1p01 / 0.5p017 / 0.5p018 / 0.5p01
Sapphire Rapids1 / 1p09 / 1p01 / 0.5p018 / 0.5p019 / 0.5p01
Zen 42 / 1FP0 FP18 / 1FP1 FP22 / 11FP0 FP18 / 0.5FP1 FP28 / 0.5FP1 FP2
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2797; AMD 58455, row 307).

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 doubleword of the result comes from the doubleword in the same place in each source.
VPROLD: element by elementResult doubleword i comes from doubleword i of xmm2. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2or m128a1110k1r0r1r3xmm1

Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m32bcst, one doubleword from memory stands for every element of the last source.

Result doubleword i comes from doubleword i of xmm2. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.

Operation

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

for i in range(VL // 32):
    if k1[i]:
        zmm1.d[i] = rol(src2.d[i], imm8, 32)
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src2.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 6 cases.

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.
OperandKindAction
VPROLD xmm {k}{z}, xmm/m128/m32bcst, imm8 VPROLD ymm {k}{z}, ymm/m256/m32bcst, imm8 VPROLD zmm {k}{z}, zmm/m512/m32bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread
imm8explicitread

Flags

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

Exceptions

The exception class is XED's name for the set of exception conditions that a form follows. How to read.

All forms
AVX512-E4

Attributes

What else XED records about the forms. How to read.

All forms
write masking
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPROLD, 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.

IntrinsicCompiles to
_mm_rol_epi32 __m128i _mm_rol_epi32(__m128i a, const int b)

VPROLD xmm, xmm, imm8 EVEX.128 -mavx512vl

_mm_ror_epi32 __m128i _mm_ror_epi32(__m128i a, const int b)

VPROLD xmm, xmm, imm8 EVEX.128 -mavx512vl

_mm_mask_rol_epi32 __m128i _mm_mask_rol_epi32(__m128i w, __mmask8 u, __m128i a, const int b)

VPROLD xmm {k}, xmm, imm8 EVEX.128 -mavx512vl

_mm_mask_ror_epi32 __m128i _mm_mask_ror_epi32(__m128i w, __mmask8 u, __m128i a, const int b)

VPROLD xmm {k}, xmm, imm8 EVEX.128 -mavx512vl

_mm_maskz_rol_epi32 __m128i _mm_maskz_rol_epi32(__mmask8 u, __m128i a, const int b)

VPROLD xmm {k}{z}, xmm, imm8 EVEX.128 -mavx512vl

_mm_maskz_ror_epi32 __m128i _mm_maskz_ror_epi32(__mmask8 u, __m128i a, const int b)

VPROLD xmm {k}{z}, xmm, imm8 EVEX.128 -mavx512vl

_mm256_rol_epi32 __m256i _mm256_rol_epi32(__m256i a, const int b)

VPROLD ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_ror_epi32 __m256i _mm256_ror_epi32(__m256i a, const int b)

VPROLD ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_mask_rol_epi32 __m256i _mm256_mask_rol_epi32(__m256i w, __mmask8 u, __m256i a, const int b)

VPROLD ymm {k}, ymm, imm8 EVEX.256 -mavx512vl

_mm256_mask_ror_epi32 __m256i _mm256_mask_ror_epi32(__m256i w, __mmask8 u, __m256i a, const int b)

VPROLD ymm {k}, ymm, imm8 EVEX.256 -mavx512vl

_mm256_maskz_rol_epi32 __m256i _mm256_maskz_rol_epi32(__mmask8 u, __m256i a, const int b)

VPROLD ymm {k}{z}, ymm, imm8 EVEX.256 -mavx512vl

_mm256_maskz_ror_epi32 __m256i _mm256_maskz_ror_epi32(__mmask8 u, __m256i a, const int b)

VPROLD ymm {k}{z}, ymm, imm8 EVEX.256 -mavx512vl

_mm512_rol_epi32 __m512i _mm512_rol_epi32(__m512i a, const int b)

VPROLD zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_ror_epi32 __m512i _mm512_ror_epi32(__m512i A, const int B)

VPROLD zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_mask_rol_epi32 __m512i _mm512_mask_rol_epi32(__m512i W, __mmask16 U, __m512i a, const int b)

VPROLD zmm {k}, zmm, imm8 EVEX.512 -mavx512f

_mm512_mask_ror_epi32 __m512i _mm512_mask_ror_epi32(__m512i W, __mmask16 U, __m512i A, const int B)

VPROLD zmm {k}, zmm, imm8 EVEX.512 -mavx512f

_mm512_maskz_rol_epi32 __m512i _mm512_maskz_rol_epi32(__mmask16 U, __m512i a, const int b)

VPROLD zmm {k}{z}, zmm, imm8 EVEX.512 -mavx512f

_mm512_maskz_ror_epi32 __m512i _mm512_maskz_ror_epi32(__mmask16 U, __m512i A, const int B)

VPROLD zmm {k}{z}, zmm, imm8 EVEX.512 -mavx512f

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 setCPUIDProcessors
AVX512F_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512F_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512F_256
Same as AVX512F_128Same as AVX512F_128

More AVX10.1 instructions

All 686 AVX10.1 instructions

Sources

  1. Intel XED v2026.08.23 (commit 0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model.
  2. The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s -march feature sets and AMD’s Processor Programming References, which the page of each processor cites.
  3. Clang's x86 intrinsic headers, LLVM 23.1.2 (commit 85ac56026243): the intrinsics, their signatures and doc comments, and the Clang of that release, which compiled each of them.
  4. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  5. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-610 (VPROLD/VPROLVD/VPROLQ/VPROLVQ)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  8. Software Optimization Guide for the AMD Zen5 Microarchitecture (58455, rev. 1.00, August 2024), Wayback Machine copy of AMD's ZIP

The tables are derived from Intel XED, Copyright Intel Corporation, licensed under the Apache License 2.0; x86-64.net converted and reformatted them. The intrinsics and their signatures come from Clang and the timings from LLVM's scheduling models, both part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.