Instruction
VPRORVQ
Rotates each quadword right by the count in the matching element of the second source.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPRORVQ rotates each quadword of its first source right by the count in the matching quadword of the second source, which may be a broadcast quadword. Only the low 6 bits of each count matter, so 40h rotates by nothing and 7Fh by 63, a rotate left by one. It is the variable form of VPRORQ and the right-hand partner of VPROLVQ, whose page covers the shifts it replaces; VPRORVD rotates doublewords. It needs AVX512F, plus AVX512VL below 512 bits, and takes a write mask.
Recorded on Zen 5
- Counts modulo 64. In
vprorvq zmm9{k2}, zmm9, zmm14, 1 rotated right by 1 became 8000000000000000h, 7FFFFFFFFFFFFFFFh rotated by 7Fh became FFFFFFFFFFFFFFFEh, and -1 rotated by 41h stayed -1. - Halves swapped. With a broadcast count of 20h,
vprorvq zmm1{k1}, zmm2, qword bcst [mem]turned 7FFFFFFFFFFFFFFFh into FFFFFFFF7FFFFFFFh and 8000000000000000h into 80000000h in the two elements K1 selects, and left the other six alone. - Register form.
{evex} vprorvq xmm7, xmm12, xmm7turned 1 rotated by 3 into 2000000000000000h and cleared XMM7 above bit 127.
In compiled code
At -O2 with -march=x86-64-v4, Clang 23 compiles
(x[i] >> s) | (x[i] << ((64 - s) & 63)) with s = c[i] & 63 over
uint64_t arrays to VPRORVQ on YMM registers, with the counts read
straight from memory. GCC 14 keeps VPSRLVQ,
VPSLLVQ and an OR on ZMM registers. Both compile
_mm512_rorv_epi64 to one VPRORVQ.
AMD’s Zen 5 latency spreadsheet gives VPRORVQ one macro-op with 2 cycles, two per cycle on pipes FP0 and FP1, as VPROLVQ.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPRORVQ zmm {k}{z}, zmm, zmm
VPRORVQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512 | EVEX.512.66.0F38.W1 14 /r | AVX10.1 or AVX512F |
VPRORVQ zmm {k}{z}, zmm, m512/m64bcst
VPRORVQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512 | EVEX.512.66.0F38.W1 14 /r | AVX10.1 or AVX512F |
VPRORVQ xmm {k}{z}, xmm, xmm
VPRORVQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512 | EVEX.128.66.0F38.W1 14 /r | AVX10.1 or AVX512F + AVX512VL |
VPRORVQ xmm {k}{z}, xmm, m128/m64bcst
VPRORVQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512 | EVEX.128.66.0F38.W1 14 /r | AVX10.1 or AVX512F + AVX512VL |
VPRORVQ ymm {k}{z}, ymm, ymm
VPRORVQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512 | EVEX.256.66.0F38.W1 14 /r | AVX10.1 or AVX512F + AVX512VL |
VPRORVQ ymm {k}{z}, ymm, m256/m64bcst
VPRORVQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512 | EVEX.256.66.0F38.W1 14 /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m64bcst | xmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | xmm {k}{z}, xmm, m128/m64bcst | ymm {k}{z}, ymm, m256/m64bcst |
|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 1 / 1p0 | 8 / 1p0 | 1 / 0.5p01 | 7 / 0.5p01 | 8 / 0.5p01 |
| Sapphire Rapids | 1 / 1p0 | 9 / 1p0 | 1 / 0.5p01 | 8 / 0.5p01 | 9 / 0.5p01 |
| Zen 4 | 2 / 1FP0 FP1 | 8 / 1FP1 FP2 | 2 / 1FP0 FP1 | 8 / 0.5FP1 FP2 | 8 / 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.
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 and xmm3. 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]:
a = zmm2.q[i]
b = src3.q[i]
zmm1.q[i] = ror(a, b, 64)
elif zeroing:
zmm1.q[i] = 0
# else: zmm1.q[i] keeps its value
# m64bcst: src3.q[i] is the m64 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPRORVQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPRORVQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPRORVQ zmm {k}{z}, zmm, zmm/m512/m64bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | explicit | read |
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 VPRORVQ, 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_rorv_epi64
__m128i _mm_rorv_epi64(__m128i __A, __m128i __B) |
|
_mm_mask_rorv_epi64
__m128i _mm_mask_rorv_epi64(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_rorv_epi64
__m128i _mm_maskz_rorv_epi64(__mmask8 __U, __m128i __A, __m128i __B) |
|
_mm256_rorv_epi64
__m256i _mm256_rorv_epi64(__m256i __A, __m256i __B) |
|
_mm256_mask_rorv_epi64
__m256i _mm256_mask_rorv_epi64(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_rorv_epi64
__m256i _mm256_maskz_rorv_epi64(__mmask8 __U, __m256i __A, __m256i __B) |
|
_mm512_rorv_epi64
__m512i _mm512_rorv_epi64(__m512i __A, __m512i __B) |
|
_mm512_mask_rorv_epi64
__m512i _mm512_mask_rorv_epi64(__m512i __W, __mmask8 __U, __m512i __A, __m512i __B) |
|
_mm512_maskz_rorv_epi64
__m512i _mm512_maskz_rorv_epi64(__mmask8 __U, __m512i __A, __m512i __B) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512F_512 | AVX10.1 or 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 or AVX512F + 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_128 | Same as AVX512F_128 |
More AVX10.1 instructions
- VPMULHUW
- VPMULHW
- VPMULLD
- VPMULLQ
- VPMULLW
- VPMULTISHIFTQB
- VPMULUDQ
- VPOPCNTB
- VPOPCNTD
- VPOPCNTQ
- VPOPCNTW
- VPORD
- VPORQ
- VPROLD
- VPROLQ
- VPROLVD
- VPROLVQ
- VPRORD
- VPRORQ
- VPRORVD
- VPSADBW
- VPSCATTERDD
- VPSCATTERDQ
- VPSCATTERQD
- VPSCATTERQQ
- VPSHLDD
- VPSHLDQ
- VPSHLDVD
- VPSHLDVQ
- VPSHLDVW
- VPSHLDW
- VPSHRDD
- VPSHRDQ
- VPSHRDVD
- VPSHRDVQ
- VPSHRDVW
- VPSHRDW
- VPSHUFB
- VPSHUFBITQMB
- VPSHUFD
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- 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) - 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.