Instruction
VPSRLVW
Shifts each word right logically by the count in the matching element of the second source.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPSRLVW shifts each word right by its own count, taken from the matching word of the second source, and fills with zeros from the left. It is the word form of VPSRLVD, added by AVX512BW; VPSLLVD describes the variable shifts, with whole unsigned counts and zero for every count from 16 up here. VPSRAVW is the arithmetic twin and VPSLLVW shifts left. It has no broadcast form.
Recorded on Zen 5
- Zeros from the left. In
vpsrlvw ymm9, ymm9, ymmword ptr [mem], 7FFFh shifted by 1 gave 3FFFh, 8000h by 15 gave 1 and FFFFh by 8 gave 00FFh, where VPSRAVW would have brought in ones for 8000h and FFFFh. - Counts from 16. In
vpsrlvw xmm9, xmm9, xmm14, FFFFh shifted by 11h and by FFFFh and 7FFFh by 8000h all gave 0; in the YMM case a count of 0 left FFFFh as it was. - Zeroing. In
vpsrlvw xmm24{k7}{z}, xmm3, xmmword ptr [mem], with E3h in K7’s low byte, FFFFh shifted by 8 gave 00FFh in word 6, and the words K7 left out were zeroed.
In compiled code
For o[i] = a[i] >> (b[i] & 15) over uint16_t arrays, GCC 14 and
Clang 23 at -O2 with -march=x86-64-v4 mask the counts with a VPANDQ
or VPAND and shift with VPSRLVW, GCC on ZMM and Clang on YMM
registers. With -march=x86-64-v3, which has no shift of words by
separate counts, GCC keeps the loop scalar with one SARX per element;
for the left shift VPSLLVW’s page shows how GCC
widens to doublewords instead.
AMD’s Zen 5 latency spreadsheet gives VPSRLVW one cycle and two per cycle on pipes FP2 and FP3, as VPSLLVW.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPSRLVW xmm {k}{z}, xmm, xmm
VPSRLVW_XMMu16_MASKmskw_XMMu16_XMMu16_AVX512 | EVEX.128.66.0F38.W1 10 /r | AVX10.1 or AVX512BW + AVX512VL |
VPSRLVW xmm {k}{z}, xmm, m128
VPSRLVW_XMMu16_MASKmskw_XMMu16_MEMu16_AVX512 | EVEX.128.66.0F38.W1 10 /r | AVX10.1 or AVX512BW + AVX512VL |
VPSRLVW ymm {k}{z}, ymm, ymm
VPSRLVW_YMMu16_MASKmskw_YMMu16_YMMu16_AVX512 | EVEX.256.66.0F38.W1 10 /r | AVX10.1 or AVX512BW + AVX512VL |
VPSRLVW ymm {k}{z}, ymm, m256
VPSRLVW_YMMu16_MASKmskw_YMMu16_MEMu16_AVX512 | EVEX.256.66.0F38.W1 10 /r | AVX10.1 or AVX512BW + AVX512VL |
VPSRLVW zmm {k}{z}, zmm, zmm
VPSRLVW_ZMMu16_MASKmskw_ZMMu16_ZMMu16_AVX512 | EVEX.512.66.0F38.W1 10 /r | AVX10.1 or AVX512BW |
VPSRLVW zmm {k}{z}, zmm, m512
VPSRLVW_ZMMu16_MASKmskw_ZMMu16_MEMu16_AVX512 | EVEX.512.66.0F38.W1 10 /r | AVX10.1 or AVX512BW |
Latency and throughput
| Model | xmm {k}{z}, xmm, xmmno maskymm {k}{z}, ymm, ymmno mask | xmm {k}{z}, xmm, xmmwith a mask, zeroingymm {k}{z}, ymm, ymmwith a mask, zeroing | xmm {k}{z}, xmm, m128no mask | xmm {k}{z}, xmm, m128with a mask, zeroing | ymm {k}{z}, ymm, m256no mask | ymm {k}{z}, ymm, m256with a mask, zeroing | zmm {k}{z}, zmm, zmmno mask | zmm {k}{z}, zmm, zmmwith a mask, zeroing | zmm {k}{z}, zmm, m512no mask | zmm {k}{z}, zmm, m512with a mask, zeroing |
|---|---|---|---|---|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 1 / 0.5p01 | 1 / 0.5p01 | 7 / 0.5p01 | 7 / 0.5p01 | 8 / 0.5p01 | 8 / 0.5p01 | 1 / 1p0 | 1 / 1p0 | 8 / 1p0 | 8 / 1p0 |
| Sapphire Rapids | 1 / 0.5p01 | 3 / 0.5p01 | 8 / 0.5p01 | 11 / 0.5p01 | 9 / 0.5p01 | 11 / 0.5p01 | 1 / 1p0 | 3 / 1p0 | 9 / 1p0 | 11 / 1p0 |
| Zen 4 | 1 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 1 / 1FP1 FP2 | 1 / 1FP1 FP2 | 8 / 1FP1 FP2 | 8 / 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.
Every word works alike: 8, 16 and 32 words 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}.
Result word i comes from word i of xmm2 and xmm3. Result words 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, 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 // 16):
if k1[i]:
zmm1.w[i] = zmm2.w[i] >> src3.w[i]
elif zeroing:
zmm1.w[i] = 0
# else: zmm1.w[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPSRLVW xmm {k}{z}, xmm, xmm/m128 VPSRLVW ymm {k}{z}, ymm, ymm/m256 VPSRLVW zmm {k}{z}, zmm, zmm/m512 | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128, ymm/m256, zmm/m512 | 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
- memory fault suppression
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VPSRLVW, 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_srlv_epi16
__m128i _mm_srlv_epi16(__m128i __A, __m128i __B) |
|
_mm_mask_srlv_epi16
__m128i _mm_mask_srlv_epi16(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_srlv_epi16
__m128i _mm_maskz_srlv_epi16(__mmask8 __U, __m128i __A, __m128i __B) |
|
_mm256_srlv_epi16
__m256i _mm256_srlv_epi16(__m256i __A, __m256i __B) |
|
_mm256_mask_srlv_epi16
__m256i _mm256_mask_srlv_epi16(__m256i __W, __mmask16 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_srlv_epi16
__m256i _mm256_maskz_srlv_epi16(__mmask16 __U, __m256i __A, __m256i __B) |
|
_mm512_srlv_epi16
__m512i _mm512_srlv_epi16(__m512i __A, __m512i __B) |
|
_mm512_mask_srlv_epi16
__m512i _mm512_mask_srlv_epi16(__m512i __W, __mmask32 __U, __m512i __A, __m512i __B) |
|
_mm512_maskz_srlv_epi16
__m512i _mm512_maskz_srlv_epi16(__mmask32 __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 |
|---|---|---|
AVX512BW_128 | AVX10.1 or AVX512BW + 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 |
AVX512BW_256 | Same as AVX512BW_128 | Same as AVX512BW_128 |
AVX512BW_512 | AVX10.1 or AVX512BW | Same as AVX512BW_128 |
More AVX10.1 instructions
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-646 (VPSRLVW/
VPSRLVD/ VPSRLVQ) - 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.