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

VPSLLVW shifts each word left by its own count, taken from the matching word of the second source, and fills with zeros from the right. It is the word form that AVX512BW added to AVX2’s variable shifts, which VPSLLVD describes: each count is the whole unsigned element, and every count from 16 up gives zero. VPSRLVW shifts right and VPSRAVW right with the sign; VPSLLW shifts every word by one count. It has no broadcast form.

Recorded on Zen 5

  • Counts to 15. In vpsllvw xmm1, xmm2, xmm3, 7FFFh shifted by 1 gave FFFEh, 000Fh by 8 gave 0F00h, and 8000h by 15 gave 0.
  • Counts from 16. 8000h by 16, 7FFFh by 17 and the counts 8000h and FFFFh all gave 0; the count is not reduced modulo 16.
  • Merging into the count register. In vpsllvw zmm7{k6}, zmm12, zmm7 the counts came from ZMM7 itself and the words K6 left out kept their old counts.

In compiled code

For o[i] = a[i] << (b[i] & 15) over uint16_t arrays, Clang 23 at -O2 with -march=x86-64-v4 masks the counts and shifts with VPSLLVW on YMM registers. GCC 14 widens both operands to doublewords with VPMOVZXWD, shifts them with VPSLLVD and joins the low words with VPERMT2W, the code it uses for the same loop with -march=x86-64-v3, where it packs with VPACKUSDW instead. For the right shift of the same operands GCC does use VPSRLVW.

AMD’s Zen 5 latency spreadsheet gives VPSLLVW one cycle and two per cycle on pipes FP2 and FP3, as VPSLLVD.

Forms

Every encoding of VPSLLVW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSLLVW xmm {k}{z}, xmm, xmm VPSLLVW_XMMu16_MASKmskw_XMMu16_XMMu16_AVX512EVEX.128.66.0F38.W1 12 /rAVX10.1 or AVX512BW + AVX512VL
VPSLLVW xmm {k}{z}, xmm, m128 VPSLLVW_XMMu16_MASKmskw_XMMu16_MEMu16_AVX512EVEX.128.66.0F38.W1 12 /rAVX10.1 or AVX512BW + AVX512VL
VPSLLVW ymm {k}{z}, ymm, ymm VPSLLVW_YMMu16_MASKmskw_YMMu16_YMMu16_AVX512EVEX.256.66.0F38.W1 12 /rAVX10.1 or AVX512BW + AVX512VL
VPSLLVW ymm {k}{z}, ymm, m256 VPSLLVW_YMMu16_MASKmskw_YMMu16_MEMu16_AVX512EVEX.256.66.0F38.W1 12 /rAVX10.1 or AVX512BW + AVX512VL
VPSLLVW zmm {k}{z}, zmm, zmm VPSLLVW_ZMMu16_MASKmskw_ZMMu16_ZMMu16_AVX512EVEX.512.66.0F38.W1 12 /rAVX10.1 or AVX512BW
VPSLLVW zmm {k}{z}, zmm, m512 VPSLLVW_ZMMu16_MASKmskw_ZMMu16_MEMu16_AVX512EVEX.512.66.0F38.W1 12 /rAVX10.1 or AVX512BW

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 {k}{z}, xmm, xmmno mask
ymm {k}{z}, ymm, ymmno mask
xmm {k}{z}, xmm, xmmwith a mask, zeroing
ymm {k}{z}, ymm, ymmwith a mask, zeroing
xmm {k}{z}, xmm, m128no maskxmm {k}{z}, xmm, m128with a mask, zeroingymm {k}{z}, ymm, m256no maskymm {k}{z}, ymm, m256with a mask, zeroingzmm {k}{z}, zmm, zmmno maskzmm {k}{z}, zmm, zmmwith a mask, zeroingzmm {k}{z}, zmm, m512no maskzmm {k}{z}, zmm, m512with a mask, zeroing
Skylake-SP, Ice Lake1 / 0.5p011 / 0.5p017 / 0.5p017 / 0.5p018 / 0.5p018 / 0.5p011 / 1p01 / 1p08 / 1p08 / 1p0
Sapphire Rapids1 / 0.5p013 / 0.5p018 / 0.5p0111 / 0.5p019 / 0.5p0111 / 0.5p011 / 1p03 / 1p09 / 1p011 / 1p0
Zen 41 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP21 / 1FP1 FP21 / 1FP1 FP28 / 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 word of the result comes from the word in the same place in each source.
VPSLLVW: element by elementResult 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.01234567xmm2a11111110k1r0r1r2r3r4r5r7xmm101234567xmm3or m128b

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]:
        a = zmm2.w[i]
        b = src3.w[i]
        zmm1.w[i] = a << b if b < 16 else 0
    elif zeroing:
        zmm1.w[i] = 0
    # else: zmm1.w[i] keeps its value
# 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
VPSLLVW xmm {k}{z}, xmm, xmm/m128 VPSLLVW ymm {k}{z}, ymm, ymm/m256 VPSLLVW zmm {k}{z}, zmm, zmm/m512
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128, ymm/m256, zmm/m512explicitread

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 VPSLLVW, 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_sllv_epi16 __m128i _mm_sllv_epi16(__m128i __A, __m128i __B)

VPSLLVW xmm, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm_mask_sllv_epi16 __m128i _mm_mask_sllv_epi16(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B)

VPSLLVW xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm_maskz_sllv_epi16 __m128i _mm_maskz_sllv_epi16(__mmask8 __U, __m128i __A, __m128i __B)

VPSLLVW xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm256_sllv_epi16 __m256i _mm256_sllv_epi16(__m256i __A, __m256i __B)

VPSLLVW ymm, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm256_mask_sllv_epi16 __m256i _mm256_mask_sllv_epi16(__m256i __W, __mmask16 __U, __m256i __A, __m256i __B)

VPSLLVW ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm256_maskz_sllv_epi16 __m256i _mm256_maskz_sllv_epi16(__mmask16 __U, __m256i __A, __m256i __B)

VPSLLVW ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm512_sllv_epi16 __m512i _mm512_sllv_epi16(__m512i __A, __m512i __B)

VPSLLVW zmm, zmm, zmm EVEX.512 -mavx512bw

_mm512_mask_sllv_epi16 __m512i _mm512_mask_sllv_epi16(__m512i __W, __mmask32 __U, __m512i __A, __m512i __B)

VPSLLVW zmm {k}, zmm, zmm EVEX.512 -mavx512bw

_mm512_maskz_sllv_epi16 __m512i _mm512_maskz_sllv_epi16(__mmask32 __U, __m512i __A, __m512i __B)

VPSLLVW zmm {k}{z}, zmm, zmm EVEX.512 -mavx512bw

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
AVX512BW_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW
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
AVX512BW_256
Same as AVX512BW_128Same as AVX512BW_128
AVX512BW_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW

Same as AVX512BW_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. 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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-636 (VPSLLVW/VPSLLVD/VPSLLVQ)
  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.