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

VPSRLVD shifts each doubleword right by its own count, taken from the matching doubleword of the second source, and fills with zeros from the left. VPSLLVD describes the variable shifts of AVX2 and AVX-512: whole unsigned counts, zero for every count from 32 up, and the compilers’ code without AVX2. VPSRAVD is the arithmetic twin, which fills with copies of the sign bit. On Zen 5, vpsrlvd ymm0, ymm13, ymm9 turned 80000000h shifted by 16 into 8000h and shifted by 3 into 10000000h, with zeros where VPSRAVD would bring in ones, and gave zero for counts 20h, 21h and 3Fh.

Fields at different positions

A constant vector of counts takes apart a word whose fields sit at different bit positions. Splitting a 32-bit word into eight 4-bit fields, out[i] = (w >> 4 * i) & 15 for i from 0 to 7, compiles in GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 to three instructions: VPBROADCASTD of w, VPSRLVD by the vector 0, 4, 8 … 28 from memory, and VPAND with 15. Over an array of such words, GCC keeps that pattern for each word, while Clang turns the loop around: it shifts eight words at a time by each of the seven counts with VPSRLD and an immediate, and interleaves the results.

The plain a[i] = b[i] >> c[i] over uint32_t arrays is one VPSRLVD per vector in both compilers, on ZMM registers in GCC with -march=x86-64-v4. For the SSE2 baseline, Clang shifts each vector four times with PSRLD, once by each element’s count moved into place with PSHUFLW, and keeps the matching element of each result; GCC keeps the loop scalar with SHR.

AMD’s latency spreadsheet for Zen 5 lists VPSRLVD, VEX or EVEX, as one macro-op with a latency of one cycle on the pipes FP2 and FP3. The quadword form is VPSRLVQ.

Forms

Every encoding of VPSRLVD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSRLVD xmm, xmm, m128 VPSRLVD_XMMdq_XMMdq_MEMdqVEX.128.66.0F38.W0 45 /rAVX2
VPSRLVD xmm, xmm, xmm VPSRLVD_XMMdq_XMMdq_XMMdqVEX.128.66.0F38.W0 45 /rAVX2
VPSRLVD ymm, ymm, m256 VPSRLVD_YMMqq_YMMqq_MEMqqVEX.256.66.0F38.W0 45 /rAVX2
VPSRLVD ymm, ymm, ymm VPSRLVD_YMMqq_YMMqq_YMMqqVEX.256.66.0F38.W0 45 /rAVX2
VPSRLVD zmm {k}{z}, zmm, zmm VPSRLVD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512EVEX.512.66.0F38.W0 45 /rAVX10.1 or AVX512F
VPSRLVD zmm {k}{z}, zmm, m512/m32bcst VPSRLVD_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512EVEX.512.66.0F38.W0 45 /rAVX10.1 or AVX512F
VPSRLVD xmm {k}{z}, xmm, xmm VPSRLVD_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512EVEX.128.66.0F38.W0 45 /rAVX10.1 or AVX512F + AVX512VL
VPSRLVD xmm {k}{z}, xmm, m128/m32bcst VPSRLVD_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512EVEX.128.66.0F38.W0 45 /rAVX10.1 or AVX512F + AVX512VL
VPSRLVD ymm {k}{z}, ymm, ymm VPSRLVD_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512EVEX.256.66.0F38.W0 45 /rAVX10.1 or AVX512F + AVX512VL
VPSRLVD ymm {k}{z}, ymm, m256/m32bcst VPSRLVD_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512EVEX.256.66.0F38.W0 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/m32bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m32bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m32bcst
Haswell9 / 2p053 / 2p0510 / 2p053 / 2p05
Broadwell8 / 2p053 / 2p059 / 2p053 / 2p05
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 doubleword of the result comes from the doubleword in the same place in each source.
VPSRLVD: 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 EVEX 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]:  # 1 without a write mask
        zmm1.d[i] = zmm2.d[i] >> src3.d[i]
    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): 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
VPSRLVD xmm, xmm, xmm/m128 VPSRLVD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPSRLVD xmm {k}{z}, xmm, xmm/m128/m32bcst VPSRLVD ymm {k}{z}, ymm, ymm/m256/m32bcst VPSRLVD 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.

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 VPSRLVD, 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_epi32 __m128i _mm_srlv_epi32(__m128i __X, __m128i __Y)

VPSRLVD xmm, xmm, xmm VEX.128 -mavx2

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

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

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

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

_mm256_srlv_epi32 __m256i _mm256_srlv_epi32(__m256i __X, __m256i __Y)

VPSRLVD ymm, ymm, ymm VEX.256 -mavx2

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

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

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

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

_mm512_srlv_epi32 __m512i _mm512_srlv_epi32(__m512i __X, __m512i __Y)

VPSRLVD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_srlv_epi32 __m512i _mm512_mask_srlv_epi32(__m512i __W, __mmask16 __U, __m512i __X, __m512i __Y)

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

_mm512_maskz_srlv_epi32 __m512i _mm512_maskz_srlv_epi32(__mmask16 __U, __m512i __X, __m512i __Y)

VPSRLVD 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. 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.