Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VPSRLVQ shifts each quadword right by its own count, taken from the matching quadword of the second source, and fills with zeros from the left. It is the 64-bit, logical, rightward member of the variable shifts that AVX2 introduced; VPSLLVD and VPSRAVD describe the family, the counts read as whole unsigned elements, and what compilers do without AVX2. For quadwords, every count from 64 up gives zero: the cases recorded on Zen 5 show zero for counts of 65, 127 and FFFFFFFFFFFFFFFFh, where SHR would mask the count to its low 6 bits.

A bitmap lookup per element

Shifting one 64-bit constant by many counts tests many bits of it at once. For d[i] = (m >> (x[i] & 63)) & 1, where m is a bitmap of 64 entries such as a set of character classes, GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 broadcast m and apply VPSRLVQ with the indices as counts, testing four entries per instruction, eight with zmm registers. The plain a[i] >> b[i] on uint64_t arrays becomes one VPSRLVQ per vector in both compilers; C leaves counts of 64 and more undefined, so the zero is never in the way.

Before AVX2

SSE2’s PSRLQ with a register count shifts both quadwords by the same count, the low quadword of the count register. For the SSE2 baseline Clang 23 still vectorizes a[i] >> b[i]: it shifts the vector twice, once by each element’s count, and keeps one half of each result. GCC 14 keeps the loop scalar with SHR. AMD’s XOP had a variable shift of its own, VPSHLQ, whose signed count shifts left when positive and right when negative; Zen 5 has no XOP.

AVX-512 adds masking, a broadcast count and the 512-bit form, and the arithmetic VPSRAVQ, which AVX2 lacks. The left shift is VPSLLVQ. AMD’s Zen 5 guide lists VPSRLVQ, VEX or EVEX, as one macro-op with a latency of one cycle.

Forms

Every encoding of VPSRLVQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSRLVQ xmm, xmm, m128 VPSRLVQ_XMMdq_XMMdq_MEMdqVEX.128.66.0F38.W1 45 /rAVX2
VPSRLVQ xmm, xmm, xmm VPSRLVQ_XMMdq_XMMdq_XMMdqVEX.128.66.0F38.W1 45 /rAVX2
VPSRLVQ ymm, ymm, m256 VPSRLVQ_YMMqq_YMMqq_MEMqqVEX.256.66.0F38.W1 45 /rAVX2
VPSRLVQ ymm, ymm, ymm VPSRLVQ_YMMqq_YMMqq_YMMqqVEX.256.66.0F38.W1 45 /rAVX2
VPSRLVQ zmm {k}{z}, zmm, zmm VPSRLVQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F38.W1 45 /rAVX10.1 or AVX512F
VPSRLVQ zmm {k}{z}, zmm, m512/m64bcst VPSRLVQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F38.W1 45 /rAVX10.1 or AVX512F
VPSRLVQ xmm {k}{z}, xmm, xmm VPSRLVQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F38.W1 45 /rAVX10.1 or AVX512F + AVX512VL
VPSRLVQ xmm {k}{z}, xmm, m128/m64bcst VPSRLVQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F38.W1 45 /rAVX10.1 or AVX512F + AVX512VL
VPSRLVQ ymm {k}{z}, ymm, ymm VPSRLVQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F38.W1 45 /rAVX10.1 or AVX512F + AVX512VL
VPSRLVQ ymm {k}{z}, ymm, m256/m64bcst VPSRLVQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F38.W1 45 /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.
Modelxmm, xmm, m128
xmm {k}{z}, xmm, m128/m64bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m64bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m64bcst
Haswell7 / 1p01 / 1p08 / 1p01 / 1p0
Broadwell6 / 1p01 / 1p07 / 1p01 / 1p0
Skylake7 / 0.5p011 / 0.5p018 / 0.5p011 / 0.5p01
Skylake-SP, Ice Lake7 / 0.5p011 / 0.5p018 / 0.5p011 / 0.5p011 / 1p08 / 1p0
Alder Lake8 / 0.5p011 / 0.5p019 / 0.5p011 / 0.5p01
Sapphire Rapids8 / 0.5p011 / 0.5p019 / 0.5p011 / 0.5p011 / 1p09 / 1p0
Lunar Lake7 / 2V0 V11 / 0.5V0 V18 / 2.33V0 V11 / 0.5V0 V1
Zen10 / 2FPU13 / 2FPU110 / 4FPU13 / 4FPU1
Zen 210 / 2FPU13 / 2FPU110 / 2FPU13 / 2FPU1
Zen 38 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP2
Zen 48 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP21 / 1FP1 FP28 / 1FP1 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 quadword of the result comes from the quadword in the same place in each source.
VPSRLVQ: element by elementResult quadword i comes from quadword i of xmm2 and xmm3. Result quadwords 1 to 0: r1, r0.01xmm2a11k1r0r1xmm101xmm3or m128b

Every quadword works alike: 2, 4 and 8 quadwords in the xmm, ymm and zmm forms. The EVEX 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]:  # 1 without a write mask
        zmm1.q[i] = zmm2.q[i] >> src3.q[i]
    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 up

Run on AMD Zen 5 (EPYC 9645): 10 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
VPSRLVQ xmm, xmm, xmm/m128 VPSRLVQ ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPSRLVQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPSRLVQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPSRLVQ zmm {k}{z}, zmm, zmm/m512/m64bcst
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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.

VEX forms
avx-type-4
EVEX forms
AVX512-E4

Attributes

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

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

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSRLVQ, 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_srlv_epi64 __m128i _mm_srlv_epi64(__m128i __X, __m128i __Y)

VPSRLVQ xmm, xmm, xmm VEX.128 -mavx2

_mm_mask_srlv_epi64 __m128i _mm_mask_srlv_epi64(__m128i __W, __mmask8 __U, __m128i __X, __m128i __Y)

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

_mm_maskz_srlv_epi64 __m128i _mm_maskz_srlv_epi64(__mmask8 __U, __m128i __X, __m128i __Y)

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

_mm256_srlv_epi64 __m256i _mm256_srlv_epi64(__m256i __X, __m256i __Y)

VPSRLVQ ymm, ymm, ymm VEX.256 -mavx2

_mm256_mask_srlv_epi64 __m256i _mm256_mask_srlv_epi64(__m256i __W, __mmask8 __U, __m256i __X, __m256i __Y)

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

_mm256_maskz_srlv_epi64 __m256i _mm256_maskz_srlv_epi64(__mmask8 __U, __m256i __X, __m256i __Y)

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

_mm512_srlv_epi64 __m512i _mm512_srlv_epi64(__m512i __X, __m512i __Y)

VPSRLVQ zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_srlv_epi64 __m512i _mm512_mask_srlv_epi64(__m512i __W, __mmask8 __U, __m512i __X, __m512i __Y)

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

_mm512_maskz_srlv_epi64 __m512i _mm512_maskz_srlv_epi64(__mmask8 __U, __m512i __X, __m512i __Y)

VPSRLVQ 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
AVX2

AVX2
CPUID.(EAX=07H,ECX=0):EBX[5] AVX2

Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
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 AVX2 instructions

All 138 AVX2 instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-646 (VPSRLVW/VPSRLVD/VPSRLVQ)
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  7. AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit, 256-Bit, and 512-Bit Media Instructions (26568, rev. 3.27, July 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.