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

VPMULLQ multiplies quadwords element by element and keeps the low 64 bits of each 128-bit product. Those bits do not depend on whether the inputs are signed or unsigned, so one instruction serves int64_t and uint64_t alike, and nothing reports a product that did not fit. It is the quadword member of the family of PMULLW and PMULLD, and the last to arrive: it needs AVX512DQ (with AVX512VL for xmm and ymm), so there is no SSE or AVX2 form, and no vector instruction gives the high half of a 64-bit product.

Before AVX-512

Without it, a 64-bit product is assembled from 32-bit pieces with PMULUDQ: the product of the low halves, plus the two cross products shifted up by 32 bits; the product of the high halves lies wholly above bit 63. For a loop over 1,024 int64_t elements, a[i] = b[i] * c[i], GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 emit three VPMULUDQs per vector, with the shifts and additions around them. With -march=x86-64-v4 the body becomes VPMULLQ: on zmm registers in GCC, and on ymm in Clang, which keeps to 256 bits unless tuned for a processor such as Zen 4 or Zen 5. Intel’s optimization guide uses the same contrast to show AVX-512’s new quadword instructions: a loop that keeps the larger of the sum and the product of two arrays takes 118 instructions with AVX2 and 30 with AVX-512 (Section 17.13.1, Example 17-22).

Multiplying by a constant

The compilers weigh VPMULLQ against shifts and additions differently. GCC 14 multiplies 64-bit elements by 10 with two shifts and an addition for x86-64-v4, Zen 5 and Sapphire Rapids alike, and uses VPMULLQ for 1234567. Clang 23 multiplies by 10 with VPMULLQ under -march=x86-64-v4 and -march=znver5, but with shifts and additions under -march=sapphirerapids or -march=skylake-avx512.

Speed

AMD’s Zen 5 guide lists VPMULLQ as one macro-op with a latency of three cycles, the same as VPMULLD. Intel’s guide names VPMULLQ among the instructions that falsely depend on their destination register in the Golden Cove microarchitecture, and recommends zeroing the destination first with a zero idiom such as VPXORD (Section 2.4.1.2).

In the optimization guide

What the optimization guide says about VPMULLQ, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Golden Cove and Raptor Cove

Ice Lake to Rocket Lake

  • Vectors and AVX-512: LLVM’s tuning for these cores counts VPMULLQ as slow: its model makes it three micro-ops with a latency of 15 cycles.

Forms

Every encoding of VPMULLQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPMULLQ xmm {k}{z}, xmm, xmm VPMULLQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F38.W1 40 /rAVX10.1 or AVX512DQ + AVX512VL
VPMULLQ xmm {k}{z}, xmm, m128/m64bcst VPMULLQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F38.W1 40 /rAVX10.1 or AVX512DQ + AVX512VL
VPMULLQ ymm {k}{z}, ymm, ymm VPMULLQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F38.W1 40 /rAVX10.1 or AVX512DQ + AVX512VL
VPMULLQ ymm {k}{z}, ymm, m256/m64bcst VPMULLQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F38.W1 40 /rAVX10.1 or AVX512DQ + AVX512VL
VPMULLQ zmm {k}{z}, zmm, zmm VPMULLQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F38.W1 40 /rAVX10.1 or AVX512DQ
VPMULLQ zmm {k}{z}, zmm, m512/m64bcst VPMULLQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F38.W1 40 /rAVX10.1 or AVX512DQ

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, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m64bcstymm {k}{z}, ymm, m256/m64bcstzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m64bcst
Skylake-SP15 / 1.5p0121 / 1.5p0122 / 1.5p0115 / 1.5p0522 / 1.5p05
Ice Lake15 / 1.5p0121 / 1.5p0122 / 1.5p0115 / 3p022 / 3p0
Sapphire Rapids15 / 1.5p0123 / 1.5p0123 / 1.5p0115 / 3p023 / 3p0
Zen 43 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP33 / 1FP0 FP310 / 1FP0 FP3

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.
VPMULLQ: element by elementResult quadword i comes from quadword i of xmm2 and xmm3. Result quadwords 1 to 0: a1×b1, a0×b0.01xmm2a11k1a0×b0a1×b1xmm101xmm3or m128b

Every quadword works alike: 2, 4 and 8 quadwords 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}. 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: a1×b1, a0×b0.

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]:
        zmm1.q[i] = zmm2.q[i] * src3.q[i]
    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): 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
VPMULLQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPMULLQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPMULLQ 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.

All forms
AVX512-E4

Attributes

What else XED records about the forms. How to read.

All forms
write masking
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPMULLQ, 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_mullo_epi64 __m128i _mm_mullo_epi64(__m128i __A, __m128i __B)

VPMULLQ xmm, xmm, xmm EVEX.128 -mavx512vl -mavx512dq

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

VPMULLQ xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512dq

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

VPMULLQ xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl -mavx512dq

_mm256_mullo_epi64 __m256i _mm256_mullo_epi64(__m256i __A, __m256i __B)

VPMULLQ ymm, ymm, ymm EVEX.256 -mavx512vl -mavx512dq

_mm256_mask_mullo_epi64 __m256i _mm256_mask_mullo_epi64(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B)

VPMULLQ ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512dq

_mm256_maskz_mullo_epi64 __m256i _mm256_maskz_mullo_epi64(__mmask8 __U, __m256i __A, __m256i __B)

VPMULLQ ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl -mavx512dq

_mm512_mullo_epi64 __m512i _mm512_mullo_epi64(__m512i __A, __m512i __B)

VPMULLQ zmm, zmm, zmm EVEX.512 -mavx512dq

_mm512_mask_mullo_epi64 __m512i _mm512_mask_mullo_epi64(__m512i __W, __mmask8 __U, __m512i __A, __m512i __B)

VPMULLQ zmm {k}, zmm, zmm EVEX.512 -mavx512dq

_mm512_maskz_mullo_epi64 __m512i _mm512_maskz_mullo_epi64(__mmask8 __U, __m512i __A, __m512i __B)

VPMULLQ zmm {k}{z}, zmm, zmm EVEX.512 -mavx512dq

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
AVX512DQ_128

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

or

AVX512DQ + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ
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
AVX512DQ_256
Same as AVX512DQ_128Same as AVX512DQ_128
AVX512DQ_512

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

or

AVX512DQ
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ

Same as AVX512DQ_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 2B, page 4-387 (PMULLD/PMULLQ)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  8. 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.