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

VMULPD multiplies doubles, two, four or eight at a time. It is MULPD in VEX and EVEX encodings; VMULPS covers what they add and how compilers fuse a multiplication and an addition into an FMA, which happens to doubles in the same way.

Rounding modes on Zen 5

The cases recorded on Zen 5 show how much the rounding mode can matter for a double:

  • With MXCSR set to round toward zero, 0.1 times 3 gave 3FD3333333333333H, the double just below the exact product, and 10^300 times 10^300 gave the largest finite double rather than infinity.
  • With MXCSR rounding up, the square of -2^-1023 gave the smallest denormal, 2^-1074, rather than 0.
  • {rd-sae} overrides MXCSR for one 512-bit instruction: with MXCSR at round to nearest, 0.1 times 0.1 gave 3F847AE147AE147BH, rounded down. DAZ still applies: a denormal input squared gave 0.
  • {rn-sae} with every exception unmasked squared the largest double to infinity without #XM and left MXCSR’s flags alone; without it, a signaling NaN under MXCSR 0 raised #XM and left the destination as it was.

Division by a constant

A division by a power of two is a multiplication by its exact reciprocal, so GCC 14 and Clang 23 at -O2 compile a[i] = b[i] / 2.0 over doubles to VMULPD by 0.5, with -march=x86-64-v3 and without any fast-math option. b[i] / 3.0 and b[i] / 0.1 stay VDIVPD, since 1/3 and 1/0.1 are not exact doubles; -ffast-math turns them into VMULPD by 0.333… and by 10, which can differ in the last bit. b[i] * 2.0 becomes VADDPD of b[i] to itself.

AMD’s Zen 5 guide lists VMULPD with the figures of VMULPS: a latency of 3 cycles on pipes FP0 and FP1, two per cycle.

In the optimization guide

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

Haswell and Broadwell

  • What Broadwell changed: Broadwell cuts the latency of floating-point multiplication from 5 cycles to 3, for SSE and AVX code and, by Intel’s manual, x87 as well; FMA stays at 5. sources differ

Zen and Zen+

  • Vectors and floating point: A float addition takes three cycles, a multiplication three in single precision and four in double, and an FMA five, each on two pipes; AMD’s spreadsheet, LLVM’s model and Agner Fog agree.

Forms

Every encoding of VMULPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMULPD xmm, xmm, m128 VMULPD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG 59 /rAVX
VMULPD xmm, xmm, xmm VMULPD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG 59 /rAVX
VMULPD ymm, ymm, m256 VMULPD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG 59 /rAVX
VMULPD ymm, ymm, ymm VMULPD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG 59 /rAVX
VMULPD zmm {k}{z}, zmm, zmm, {er} VMULPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F.W1 59 /rAVX10.1 or AVX512F
VMULPD zmm {k}{z}, zmm, m512/m64bcst VMULPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F.W1 59 /rAVX10.1 or AVX512F
VMULPD xmm {k}{z}, xmm, xmm VMULPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F.W1 59 /rAVX10.1 or AVX512F + AVX512VL
VMULPD xmm {k}{z}, xmm, m128/m64bcst VMULPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F.W1 59 /rAVX10.1 or AVX512F + AVX512VL
VMULPD ymm {k}{z}, ymm, ymm VMULPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F.W1 59 /rAVX10.1 or AVX512F + AVX512VL
VMULPD ymm {k}{z}, ymm, m256/m64bcst VMULPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F.W1 59 /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, zmm, {er}zmm {k}{z}, zmm, m512/m64bcst
Sandy Bridge11 / 1p05 / 1p012 / 1p05 / 1p0
Haswell11 / 0.5p015 / 0.5p0112 / 0.5p015 / 0.5p01
Broadwell8 / 0.5p013 / 0.5p019 / 0.5p013 / 0.5p01
Skylake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p01
Skylake-SP10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 0.5p0511 / 0.5p05
Ice Lake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 1p011 / 1p0
Alder Lake11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p014 / 1p012 / 1p0
Lunar Lake9 / 2V0 V13 / 1.5V0 V110 / 2.33V0 V13 / 1.5V0 V1
Piledriver10 / 1.5FPFMA FPU15 / 1FPFMA FPU110 / 1.5FPFMA FPU15 / 1FPFMA FPU1
Zen11 / 0.5FPU0 FPU14 / 0.5FPU0 FPU111 / 1FPU0 FPU14 / 1FPU0 FPU1
Zen 210 / 0.5FPU0 FPU13 / 0.5FPU0 FPU110 / 0.5FPU0 FPU13 / 0.5FPU0 FPU1
Zen 310 / 0.5FP0 FP13 / 0.5FP0 FP110 / 0.5FP0 FP13 / 0.5FP0 FP1
Zen 410 / 0.5FP0 FP13 / 0.5FP0 FP110 / 0.5FP0 FP13 / 0.5FP0 FP13 / 1FP0 FP110 / 1FP0 FP1
Jaguar9 / 2FPM FPU14 / 2FPM FPU19 / 4FPM FPU14 / 4FPM FPU1

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 double of the result comes from the double in the same place in each source.
VMULPD: element by elementResult double i comes from double i of xmm2 and xmm3. Result doubles 1 to 0: a1×b1, a0×b0.01xmm2a11k1a0×b0a1×b1xmm101xmm3or m128b

Every double works alike: 2, 4 and 8 doubles 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 double from memory stands for every element of the last source.

Result double i comes from double i of xmm2 and xmm3. Result doubles 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]:  # 1 without a write mask
        a = zmm2.f64[i]
        b = src3.f64[i]
        zmm1.f64[i] = mul(a, b)
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# m64bcst: src3.f64[i] is the m64 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 48 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
VMULPD xmm, xmm, xmm/m128 VMULPD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VMULPD xmm {k}{z}, xmm, xmm/m128/m64bcst VMULPD ymm {k}{z}, ymm, ymm/m256/m64bcst VMULPD zmm {k}{z}, zmm, zmm/m512/m64bcst, {er}
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-2
EVEX forms
AVX512-E2

Attributes

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

All forms
follows MXCSR
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 VMULPD, 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_mul_pd __m128d _mm_mul_pd(__m128d __a, __m128d __b)

VMULPD xmm, xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_mul_pd __m128d _mm_mask_mul_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B)

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

_mm_maskz_mul_pd __m128d _mm_maskz_mul_pd(__mmask8 __U, __m128d __A, __m128d __B)

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

_mm256_mul_pd __m256d _mm256_mul_pd(__m256d __a, __m256d __b)

VMULPD ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_mul_pd __m256d _mm256_mask_mul_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B)

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

_mm256_maskz_mul_pd __m256d _mm256_maskz_mul_pd(__mmask8 __U, __m256d __A, __m256d __B)

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

_mm512_mul_pd __m512d _mm512_mul_pd(__m512d __a, __m512d __b)

VMULPD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mul_round_pd __m512d _mm512_mul_round_pd(__m512d A, __m512d B, const int R)

VMULPD zmm, zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_mask_mul_pd __m512d _mm512_mask_mul_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B)

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

_mm512_mask_mul_round_pd __m512d _mm512_mask_mul_round_pd(__m512d W, __mmask8 U, __m512d A, __m512d B, const int R)

VMULPD zmm {k}, zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_maskz_mul_pd __m512d _mm512_maskz_mul_pd(__mmask8 __U, __m512d __A, __m512d __B)

VMULPD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_mul_round_pd __m512d _mm512_maskz_mul_round_pd(__mmask8 U, __m512d A, __m512d B, const int R)

VMULPD zmm {k}{z}, zmm, zmm, {er} 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
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, 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, Bulldozer, Piledriver, 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 AVX instructions

All 253 AVX 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 2B, page 4-142 (MULPD)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 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.