Instruction
VPSLLVQ
Shifts each quadword left by the count in the matching element of the second source.
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
| Instruction | Encoding | Requires |
|---|---|---|
VPSLLVQ xmm, xmm, m128
VPSLLVQ_XMMdq_XMMdq_MEMdq | VEX.128.66.0F38.W1 47 /r | AVX2 |
VPSLLVQ xmm, xmm, xmm
VPSLLVQ_XMMdq_XMMdq_XMMdq | VEX.128.66.0F38.W1 47 /r | AVX2 |
VPSLLVQ ymm, ymm, m256
VPSLLVQ_YMMqq_YMMqq_MEMqq | VEX.256.66.0F38.W1 47 /r | AVX2 |
VPSLLVQ ymm, ymm, ymm
VPSLLVQ_YMMqq_YMMqq_YMMqq | VEX.256.66.0F38.W1 47 /r | AVX2 |
VPSLLVQ zmm {k}{z}, zmm, zmm
VPSLLVQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512 | EVEX.512.66.0F38.W1 47 /r | AVX10.1 or AVX512F |
VPSLLVQ zmm {k}{z}, zmm, m512/m64bcst
VPSLLVQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512 | EVEX.512.66.0F38.W1 47 /r | AVX10.1 or AVX512F |
VPSLLVQ xmm {k}{z}, xmm, xmm
VPSLLVQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512 | EVEX.128.66.0F38.W1 47 /r | AVX10.1 or AVX512F + AVX512VL |
VPSLLVQ xmm {k}{z}, xmm, m128/m64bcst
VPSLLVQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512 | EVEX.128.66.0F38.W1 47 /r | AVX10.1 or AVX512F + AVX512VL |
VPSLLVQ ymm {k}{z}, ymm, ymm
VPSLLVQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512 | EVEX.256.66.0F38.W1 47 /r | AVX10.1 or AVX512F + AVX512VL |
VPSLLVQ ymm {k}{z}, ymm, m256/m64bcst
VPSLLVQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512 | EVEX.256.66.0F38.W1 47 /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m64bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m64bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m64bcst |
|---|---|---|---|---|---|---|
| Haswell | 7 / 1p0 | 1 / 1p0 | 8 / 1p0 | 1 / 1p0 | ||
| Broadwell | 6 / 1p0 | 1 / 1p0 | 7 / 1p0 | 1 / 1p0 | ||
| Skylake | 7 / 0.5p01 | 1 / 0.5p01 | 8 / 0.5p01 | 1 / 0.5p01 | ||
| Skylake-SP, Ice Lake | 7 / 0.5p01 | 1 / 0.5p01 | 8 / 0.5p01 | 1 / 0.5p01 | 1 / 1p0 | 8 / 1p0 |
| Alder Lake | 8 / 0.5p01 | 1 / 0.5p01 | 9 / 0.5p01 | 1 / 0.5p01 | ||
| Sapphire Rapids | 8 / 0.5p01 | 1 / 0.5p01 | 9 / 0.5p01 | 1 / 0.5p01 | 1 / 1p0 | 9 / 1p0 |
| Lunar Lake | 7 / 2V0 V1 | 1 / 0.5V0 V1 | 8 / 2.33V0 V1 | 1 / 0.5V0 V1 | ||
| Zen | 10 / 2FPU1 | 3 / 2FPU1 | 10 / 4FPU1 | 3 / 4FPU1 | ||
| Zen 2 | 10 / 2FPU1 | 3 / 2FPU1 | 10 / 2FPU1 | 3 / 2FPU1 | ||
| Zen 3 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | ||
| Zen 4 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 1 / 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 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 upRun on AMD Zen 5 (EPYC 9645): 10 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPSLLVQ xmm, xmm, xmm/m128 VPSLLVQ ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
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, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | 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.
- 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.
| Intrinsic | Compiles to |
|---|---|
_mm_sllv_epi64
__m128i _mm_sllv_epi64(__m128i __X, __m128i __Y) |
|
_mm_mask_sllv_epi64
__m128i _mm_mask_sllv_epi64(__m128i __W, __mmask8 __U, __m128i __X, __m128i __Y) |
|
_mm_maskz_sllv_epi64
__m128i _mm_maskz_sllv_epi64(__mmask8 __U, __m128i __X, __m128i __Y) |
|
_mm256_sllv_epi64
__m256i _mm256_sllv_epi64(__m256i __X, __m256i __Y) |
|
_mm256_mask_sllv_epi64
__m256i _mm256_mask_sllv_epi64(__m256i __W, __mmask8 __U, __m256i __X, __m256i __Y) |
|
_mm256_maskz_sllv_epi64
__m256i _mm256_maskz_sllv_epi64(__mmask8 __U, __m256i __X, __m256i __Y) |
|
_mm512_sllv_epi64
__m512i _mm512_sllv_epi64(__m512i __X, __m512i __Y) |
|
_mm512_mask_sllv_epi64
__m512i _mm512_mask_sllv_epi64(__m512i __W, __mmask8 __U, __m512i __X, __m512i __Y) |
|
_mm512_maskz_sllv_epi64
__m512i _mm512_maskz_sllv_epi64(__mmask8 __U, __m512i __X, __m512i __Y) |
|
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.
More AVX2 instructions
- VPMULDQ
- VPMULHRSW
- VPMULHUW
- VPMULHW
- VPMULLD
- VPMULLW
- VPMULUDQ
- VPOR
- VPSADBW
- VPSHUFB
- VPSHUFD
- VPSHUFHW
- VPSHUFLW
- VPSIGNB
- VPSIGND
- VPSIGNW
- VPSLLD
- VPSLLDQ
- VPSLLQ
- VPSLLVD
- VPSLLW
- VPSRAD
- VPSRAVD
- VPSRAW
- VPSRLD
- VPSRLDQ
- VPSRLQ
- VPSRLVD
- VPSRLVQ
- VPSRLW
- VPSUBB
- VPSUBD
- VPSUBQ
- VPSUBSB
- VPSUBSW
- VPSUBUSB
- VPSUBUSW
- VPSUBW
- VPUNPCKHBW
- VPUNPCKHDQ
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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-636 (VPSLLVW/
VPSLLVD/ VPSLLVQ) - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- 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.