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

VPSLLVQ shifts each quadword left by its own count, taken from the matching quadword of the second source, and fills with zeros from the right. It is the 64-bit member of the variable shifts that AVX2 introduced; VPSLLVD and VPSRLVQ describe the family, the counts read as whole unsigned elements, and what compilers do without AVX2. Every count from 64 up gives zero: the cases recorded on Zen 5 show zero for counts 40h, 41h, 7Fh, 8000000000000000h and FFFFFFFFFFFFFFFFh, while 3Fh turned an all-ones quadword into 8000000000000000h. With a write mask and a broadcast count, vpsllvq zmm7{k3}, zmm12, qword bcst [mem] applied a count of 8000000000000000h to the six elements K3 selects, zeroing them, and kept the other two.

One bit per element

Setting bit n of a 64-bit word, d[i] = 1ull << (x[i] & 63), is how code builds masks for bitsets and bitboards. Clang 23 at -O2 with -march=x86-64-v3 vectorizes it as a VPAND of the indices with 63 and VPSLLVQ of a vector of ones, four per instruction; with 32-bit indices it widens them first with VPMOVZXDQ. GCC 14 keeps the loop scalar with SHLX, and drops the AND, since SHLX masks its count to six bits itself. VPSLLVQ does not, so in vector code the AND stays.

The plain a[i] = b[i] << c[i] over uint64_t arrays is one VPSLLVQ per vector in both compilers, with the counts read from memory in Clang. GCC 14 first ANDs every count with a broadcast FFFFFFFFh, which changes no count below 64, the only ones C defines; with -march=x86-64-v4 it does the same on ZMM registers.

The arithmetic right shift of quadwords, VPSRAVQ, came only with AVX-512. AMD’s latency spreadsheet for Zen 5 lists VPSLLVQ, VEX or EVEX, as one macro-op with a latency of one cycle on the pipes FP2 and FP3.

Forms

Every encoding of VPSLLVQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSLLVQ xmm, xmm, m128 VPSLLVQ_XMMdq_XMMdq_MEMdqVEX.128.66.0F38.W1 47 /rAVX2
VPSLLVQ xmm, xmm, xmm VPSLLVQ_XMMdq_XMMdq_XMMdqVEX.128.66.0F38.W1 47 /rAVX2
VPSLLVQ ymm, ymm, m256 VPSLLVQ_YMMqq_YMMqq_MEMqqVEX.256.66.0F38.W1 47 /rAVX2
VPSLLVQ ymm, ymm, ymm VPSLLVQ_YMMqq_YMMqq_YMMqqVEX.256.66.0F38.W1 47 /rAVX2
VPSLLVQ zmm {k}{z}, zmm, zmm VPSLLVQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F38.W1 47 /rAVX10.1 or AVX512F
VPSLLVQ zmm {k}{z}, zmm, m512/m64bcst VPSLLVQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F38.W1 47 /rAVX10.1 or AVX512F
VPSLLVQ xmm {k}{z}, xmm, xmm VPSLLVQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F38.W1 47 /rAVX10.1 or AVX512F + AVX512VL
VPSLLVQ xmm {k}{z}, xmm, m128/m64bcst VPSLLVQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F38.W1 47 /rAVX10.1 or AVX512F + AVX512VL
VPSLLVQ ymm {k}{z}, ymm, ymm VPSLLVQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F38.W1 47 /rAVX10.1 or AVX512F + AVX512VL
VPSLLVQ ymm {k}{z}, ymm, m256/m64bcst VPSLLVQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F38.W1 47 /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.
VPSLLVQ: 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
        a = zmm2.q[i]
        b = src3.q[i]
        zmm1.q[i] = a << b if b < 64 else 0
    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
VPSLLVQ xmm, xmm, xmm/m128 VPSLLVQ ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPSLLVQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPSLLVQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPSLLVQ 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 VPSLLVQ, 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_epi64 __m128i _mm_sllv_epi64(__m128i __X, __m128i __Y)

VPSLLVQ xmm, xmm, xmm VEX.128 -mavx2

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

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

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

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

_mm256_sllv_epi64 __m256i _mm256_sllv_epi64(__m256i __X, __m256i __Y)

VPSLLVQ ymm, ymm, ymm VEX.256 -mavx2

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

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

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

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

_mm512_sllv_epi64 __m512i _mm512_sllv_epi64(__m512i __X, __m512i __Y)

VPSLLVQ zmm, zmm, zmm EVEX.512 -mavx512f

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

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

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

VPSLLVQ 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-636 (VPSLLVW/VPSLLVD/VPSLLVQ)
  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.