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

VPRORQ rotates each quadword right by the count in its immediate, of which only the low 6 bits count. A rotate right by n is a rotate left by 64 - n, so it does nothing that VPROLQ cannot do with another immediate, and that page covers the uses. Its doubleword form is VPRORD, and VPRORVQ takes a count per element from a register.

Recorded on Zen 5

  • {evex} vprorq xmm17, xmm30, 0x20 swapped the two doublewords of each quadword: 0Fh became F00000000h.
  • 7Fh and FFh both act as 63, a rotate left by one: vprorq ymm5{k7}{z}, ymm5, 0x7f turned 7FFFFFFFFFFFFFFFh into FFFFFFFFFFFFFFFEh, and vprorq ymm24{k6}, [mem], 0xff did the same to the element K6 selects.
  • A count of 0 copies the source: vprorq zmm24{k4}, zmm3, 0 wrote the elements of ZMM3 unchanged where K4 selects them.

Compilers prefer VPROLQ

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 turn rotates right into VPROLQ. Over a uint64_t array, (x >> 7) | (x << 57) becomes VPROLQ by 57, and the intrinsics _mm512_ror_epi64, _mm256_ror_epi64 and the merging and zeroing _mm512_mask_ror_epi64 and _mm512_maskz_ror_epi64 with 13 become VPROLQ by 51. GCC emits VPRORQ only when the count does not fit, passing _mm512_ror_epi64(x, 64) to the assembler as vprorq zmm0, zmm0, 64; Clang returns the source unchanged for 64, with no instruction, and reduces 70 to a VPROLQ by 58. With a count per element, _mm512_rorv_epi64 is VPRORVQ in both.

AMD’s Zen 5 latency spreadsheet gives VPRORQ what it gives VPROLQ: 2 cycles and two per cycle on pipes FP0 and FP1. Zen 5’s 6 recorded cases cover the register, memory and broadcast forms at all three widths.

Forms

Every encoding of VPRORQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPRORQ zmm {k}{z}, zmm, imm8 VPRORQ_ZMMu64_MASKmskw_ZMMu64_IMM8_AVX512EVEX.512.66.0F.W1 72 /0 ibAVX10.1 or AVX512F
VPRORQ zmm {k}{z}, m512/m64bcst, imm8 VPRORQ_ZMMu64_MASKmskw_MEMu64_IMM8_AVX512EVEX.512.66.0F.W1 72 /0 ibAVX10.1 or AVX512F
VPRORQ xmm {k}{z}, xmm, imm8 VPRORQ_XMMu64_MASKmskw_XMMu64_IMM8_AVX512EVEX.128.66.0F.W1 72 /0 ibAVX10.1 or AVX512F + AVX512VL
VPRORQ xmm {k}{z}, m128/m64bcst, imm8 VPRORQ_XMMu64_MASKmskw_MEMu64_IMM8_AVX512EVEX.128.66.0F.W1 72 /0 ibAVX10.1 or AVX512F + AVX512VL
VPRORQ ymm {k}{z}, ymm, imm8 VPRORQ_YMMu64_MASKmskw_YMMu64_IMM8_AVX512EVEX.256.66.0F.W1 72 /0 ibAVX10.1 or AVX512F + AVX512VL
VPRORQ ymm {k}{z}, m256/m64bcst, imm8 VPRORQ_YMMu64_MASKmskw_MEMu64_IMM8_AVX512EVEX.256.66.0F.W1 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/m64bcst, imm8xmm {k}{z}, xmm, imm8
ymm {k}{z}, ymm, imm8
xmm {k}{z}, m128/m64bcst, imm8ymm {k}{z}, m256/m64bcst, 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 2812; AMD 58455, row 332).

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 quadword of the result comes from the quadword in the same place in each source.
VPRORQ: element by elementResult quadword i comes from quadword i of xmm2. Result quadwords 1 to 0: r1, r0.01xmm2or m128a11k1r0r1xmm1

Every quadword works alike: 2, 4 and 8 quadwords 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 m64bcst, one quadword from memory stands for every element of the last source.

Result quadword i comes from quadword i of xmm2. Result quadwords 1 to 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 // 64):
    if k1[i]:
        zmm1.q[i] = ror(src2.q[i], imm8, 64)
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src2.q[i] is the m64 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
VPRORQ xmm {k}{z}, xmm/m128/m64bcst, imm8 VPRORQ ymm {k}{z}, ymm/m256/m64bcst, imm8 VPRORQ zmm {k}{z}, zmm/m512/m64bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread
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. 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.