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

VPRORD rotates each doubleword right by the count in its immediate, of which only the low 5 bits count: the bits that leave at the bottom come back in at the top. A rotate right by n is a rotate left by 32 - n, so it does nothing VPROLD cannot do with another immediate, and that page covers the uses; VPRORQ rotates quadwords, and VPRORVD takes a count per element from a register. It is AVX-512F’s, with masking and a broadcast source.

Recorded on Zen 5

  • One bit. vprord xmm14, xmm8, 0x1 turned 00000001h into 80000000h and 7FFFFFFFh into BFFFFFFFh.
  • Counts taken modulo 32. 20h rotated by nothing: in vprord zmm17{k3}, zmm30, 0x20 every selected element came out as it went in. 1Fh and 3Fh both rotated by 31, a rotate left by one: the broadcast 1 became 2, and 7FFFFFFFh became FFFFFFFEh.
  • A half turn. The broadcast 7FFFFFFFh rotated by 10h gave FFFF7FFFh, its two words swapped.

Not from compilers

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 turn every rotate by a constant into VPROLD: (x >> 7) | (x << 25) over uint32_t arrays and the intrinsic _mm512_ror_epi32(a, 7) alike become vprold ..., 25, and _mm256_ror_epi32(a, 8) becomes vprold ymm0, ymm0, 24. VPRORD therefore appears where assembly is written by hand, as in code that follows a specification stated with right rotations, such as the SHA-256 functions of FIPS 180-4. For a count in a variable Clang emits VPRORVD with the count broadcast, and GCC two shifts and VPORD.

AMD’s Zen 5 latency spreadsheet gives VPRORD 2 cycles of latency and two per cycle on pipes FP0 and FP1, as VPROLD.

Forms

Every encoding of VPRORD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPRORD zmm {k}{z}, zmm, imm8 VPRORD_ZMMu32_MASKmskw_ZMMu32_IMM8_AVX512EVEX.512.66.0F.W0 72 /0 ibAVX10.1 or AVX512F
VPRORD zmm {k}{z}, m512/m32bcst, imm8 VPRORD_ZMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.512.66.0F.W0 72 /0 ibAVX10.1 or AVX512F
VPRORD xmm {k}{z}, xmm, imm8 VPRORD_XMMu32_MASKmskw_XMMu32_IMM8_AVX512EVEX.128.66.0F.W0 72 /0 ibAVX10.1 or AVX512F + AVX512VL
VPRORD xmm {k}{z}, m128/m32bcst, imm8 VPRORD_XMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.128.66.0F.W0 72 /0 ibAVX10.1 or AVX512F + AVX512VL
VPRORD ymm {k}{z}, ymm, imm8 VPRORD_YMMu32_MASKmskw_YMMu32_IMM8_AVX512EVEX.256.66.0F.W0 72 /0 ibAVX10.1 or AVX512F + AVX512VL
VPRORD ymm {k}{z}, m256/m32bcst, imm8 VPRORD_YMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.256.66.0F.W0 72 /0 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 / 1FP0 FP18 / 0.5FP1 FP28 / 0.5FP1 FP2

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.
VPRORD: 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] = ror(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
VPRORD xmm {k}{z}, xmm/m128/m32bcst, imm8 VPRORD ymm {k}{z}, ymm/m256/m32bcst, imm8 VPRORD 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

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. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  4. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-614 (VPRORD/VPRORVD/VPRORQ/VPRORVQ)
  6. NIST FIPS 180-4: Secure Hash Standard (SHS) (August 2015)
  7. 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 timings come from LLVM's scheduling models, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.