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

VPRORVD rotates each doubleword of its first source right by the count in the matching doubleword of the second source, which may be a broadcast doubleword. Only the low 5 bits of each count matter. A rotate right by n is a rotate left by 32 - n, so it adds nothing that VPROLVD cannot do with other counts; it saves the subtraction when the counts are given for the right. It is the variable form of VPRORD, and VPRORVQ rotates quadwords. It needs AVX512F, plus AVX512VL below 512 bits, and takes a write mask.

Recorded on Zen 5

  • Plain rotates. {evex} vprorvd xmm14, xmm8, xmm29 turned 7FFFFFFFh rotated by 16 into FFFF7FFFh and 80000000h rotated by 3 into 10000000h, and left 7FFFFFFFh as it was for a count of 0.
  • Counts modulo 32. In vprorvd ymm0{k3}{z}, ymm31, ymm16, the count FFFFFFFFh rotated 1 right by 31 into 2, 1Fh rotated 8 into 10h, and 80000000h left 1 as it was. Elements 2 and 4, which K3 does not select, became zero.
  • Merging. vprorvd zmm1{k1}, zmm2, zmm3 wrote only the five elements K1 selects and kept the other eleven.

In compiled code

At -O2 with -march=x86-64-v4, Clang 23 compiles (x[i] >> s) | (x[i] << ((32 - s) & 31)) with s = c[i] & 31 over uint32_t arrays to VPRORVD on YMM registers, and broadcasts a single count for the whole loop to use VPRORVD as well. GCC 14 keeps VPSRLVD, VPSLLVD and an OR, or VPSRLD and VPSLLD for the single count. Both compile _mm512_rorv_epi32 to one VPRORVD.

AMD’s Zen 5 latency spreadsheet gives VPRORVD one macro-op with 2 cycles, two per cycle on pipes FP0 and FP1, as the left rotates.

Forms

Every encoding of VPRORVD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPRORVD zmm {k}{z}, zmm, zmm VPRORVD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512EVEX.512.66.0F38.W0 14 /rAVX10.1 or AVX512F
VPRORVD zmm {k}{z}, zmm, m512/m32bcst VPRORVD_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512EVEX.512.66.0F38.W0 14 /rAVX10.1 or AVX512F
VPRORVD xmm {k}{z}, xmm, xmm VPRORVD_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512EVEX.128.66.0F38.W0 14 /rAVX10.1 or AVX512F + AVX512VL
VPRORVD xmm {k}{z}, xmm, m128/m32bcst VPRORVD_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512EVEX.128.66.0F38.W0 14 /rAVX10.1 or AVX512F + AVX512VL
VPRORVD ymm {k}{z}, ymm, ymm VPRORVD_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512EVEX.256.66.0F38.W0 14 /rAVX10.1 or AVX512F + AVX512VL
VPRORVD ymm {k}{z}, ymm, m256/m32bcst VPRORVD_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512EVEX.256.66.0F38.W0 14 /rAVX10.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, zmmzmm {k}{z}, zmm, m512/m32bcstxmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m32bcstymm {k}{z}, ymm, m256/m32bcst
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.
VPRORVD: element by elementResult doubleword i comes from doubleword i of xmm2 and xmm3. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2a1110k1r0r1r3xmm10123xmm3or m128b

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 and xmm3. 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]:
        a = zmm2.d[i]
        b = src3.d[i]
        zmm1.d[i] = ror(a, b, 32)
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src3.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
VPRORVD xmm {k}{z}, xmm, xmm/m128/m32bcst VPRORVD ymm {k}{z}, ymm, ymm/m256/m32bcst VPRORVD zmm {k}{z}, zmm, zmm/m512/m32bcst
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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 VPRORVD, 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_rorv_epi32 __m128i _mm_rorv_epi32(__m128i __A, __m128i __B)

VPRORVD xmm, xmm, xmm EVEX.128 -mavx512vl

_mm_mask_rorv_epi32 __m128i _mm_mask_rorv_epi32(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B)

VPRORVD xmm {k}, xmm, xmm EVEX.128 -mavx512vl

_mm_maskz_rorv_epi32 __m128i _mm_maskz_rorv_epi32(__mmask8 __U, __m128i __A, __m128i __B)

VPRORVD xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl

_mm256_rorv_epi32 __m256i _mm256_rorv_epi32(__m256i __A, __m256i __B)

VPRORVD ymm, ymm, ymm EVEX.256 -mavx512vl

_mm256_mask_rorv_epi32 __m256i _mm256_mask_rorv_epi32(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B)

VPRORVD ymm {k}, ymm, ymm EVEX.256 -mavx512vl

_mm256_maskz_rorv_epi32 __m256i _mm256_maskz_rorv_epi32(__mmask8 __U, __m256i __A, __m256i __B)

VPRORVD ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm512_rorv_epi32 __m512i _mm512_rorv_epi32(__m512i __A, __m512i __B)

VPRORVD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_rorv_epi32 __m512i _mm512_mask_rorv_epi32(__m512i __W, __mmask16 __U, __m512i __A, __m512i __B)

VPRORVD zmm {k}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_rorv_epi32 __m512i _mm512_maskz_rorv_epi32(__mmask16 __U, __m512i __A, __m512i __B)

VPRORVD zmm {k}{z}, zmm, zmm 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-614 (VPRORD/VPRORVD/VPRORQ/VPRORVQ)
  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 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.