Instruction
VMULSD
Multiplies the low doubles; the other elements come from the first source.
VMULSD is MULSD in VEX and EVEX encodings: the product of the low doubles of its two sources, with the high double copied from the first source and the bits above 127 cleared. The MULSD page covers Horner’s rule and what FMA changes in it, VMULSS where a product survives once FMA is available, and VADDSS what the encodings change. The VEX form needs AVX, the EVEX form AVX-512F or AVX10.1.
An exact product of two floats
A single has a 24-bit significand, so the product of two singles needs
at most 48 bits and fits a double’s 53 exactly. (double)a * b with
float a and b is therefore the exact product: in our builds with
-march=x86-64-v3 or x86-64-v4, GCC 14 and Clang 23 at -O2 widen
both with VCVTSS2SD, each in place
(vcvtss2sd xmm0, xmm0, xmm0), and multiply with VMULSD. The double’s
wider exponent range also rules out the overflow and underflow that the
same product can meet as a float.
On Zen 5
vmulsd xmm7, xmm11, qword ptr [mem], under MXCSR 7F80H (round toward zero), multiplied -1 by -0 and gave +0: the sign of a zero product follows the signs of the factors, whatever the rounding.vmulsd xmm7{k4}, xmm12, xmm7, {rd-sae}, with bit 0 of K4 set, multiplied the quiet NaN 7FF8000000012345H by 1 and returned it, with the high double, 1, from XMM12 rather than XMM7, whose high double was that NaN.vmulsd xmm0{k7}{z}, xmm31, qword ptr [mem], with bit 0 of K7 set, gave 1 times 0 as +0 and took the high double, -1, from XMM31.
AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows 3 cycles on pipes FP0 and FP1, the figures of MULSD.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VMULSD xmm, xmm, m64
VMULSD_XMMdq_XMMdq_MEMq | VEX.LIG.F2.0F.WIG 59 /r | AVX |
VMULSD xmm, xmm, xmm
VMULSD_XMMdq_XMMdq_XMMq | VEX.LIG.F2.0F.WIG 59 /r | AVX |
VMULSD xmm {k}{z}, xmm, xmm, {er}
VMULSD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512 | EVEX.LIG.F2.0F.W1 59 /r | AVX10.1 or AVX512F |
VMULSD xmm {k}{z}, xmm, m64
VMULSD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512 | EVEX.LIG.F2.0F.W1 59 /r | AVX10.1 or AVX512F |
Latency and throughput
| Model | xmm, xmm, m64xmm {k}{z}, xmm, m64 | xmm, xmm, xmmxmm {k}{z}, xmm, xmm, {er} |
|---|---|---|
| Sandy Bridge | 11 / 1p0 | 5 / 1p0 |
| Haswell | 10 / 0.5p01 | 5 / 0.5p01 |
| Broadwell | 8 / 0.5p01 | 3 / 0.5p01 |
| Skylake, Skylake-SP, Ice Lake | 9 / 0.5p01 | 4 / 0.5p01 |
| Alder Lake, Sapphire Rapids | 11 / 0.5p01 | 4 / 0.5p01 |
| Lunar Lake | 9 / 2V0 V1 | 3 / 1.5V0 V1 |
| Piledriver | 10 / 1.5FPFMA FPU1 | 5 / 1FPFMA FPU1 |
| Zen | 11 / 0.5FPU0 FPU1 | 4 / 0.5FPU0 FPU1 |
| Zen 2 | 10 / 0.5FPU0 FPU1 | 3 / 0.5FPU0 FPU1 |
| Zen 3, Zen 4 | 10 / 0.5FP0 FP1 | 3 / 0.5FP0 FP1 |
| Jaguar | 9 / 2FPM FPU1 | 4 / 2FPM 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.
The write mask k1 applies to the low double: with bit 0 clear it keeps its old value, or is zeroed with {z}.
Result double 0 is computed from double 0 of xmm2 and xmm3; double 1 is that of xmm2. Result doubles 1 to 0: a1, a0×b0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
if k1[0]: # 1 without a write mask
a = xmm2.f64[0]
b = src3.f64[0]
xmm1.f64[0] = mul(a, b)
elif zeroing:
xmm1.f64[0] = 0
# else: xmm1.f64[0] keeps its value
xmm1.q[1] = xmm2.q[1]
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VMULSD xmm, xmm, xmm/m64 | ||
xmm | explicit | write |
xmm | explicit | read |
xmm/m64 | explicit | read |
VMULSD xmm {k}{z}, xmm, xmm/m64, {er} | ||
xmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm | explicit | read |
xmm/m64 | 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-3- EVEX forms
AVX512-E3
Attributes
What else XED records about the forms. How to read.
- All forms
- follows MXCSR
- EVEX forms
- write masking
- EVEX memory forms
- memory fault suppression
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VMULSD, 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_mul_round_sd
__m128d _mm_mul_round_sd(__m128d A, __m128d B, const int R) |
|
_mm_mul_sd
__m128d _mm_mul_sd(__m128d __a, __m128d __b) |
|
_mm_mask_mul_round_sd
__m128d _mm_mask_mul_round_sd(__m128d W, __mmask8 U, __m128d A, __m128d B, const int R) |
|
_mm_mask_mul_sd
__m128d _mm_mask_mul_sd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B) |
|
_mm_maskz_mul_round_sd
__m128d _mm_maskz_mul_round_sd(__mmask8 U, __m128d A, __m128d B, const int R) |
|
_mm_maskz_mul_sd
__m128d _mm_maskz_mul_sd(__mmask8 __U, __m128d __A, __m128d __B) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX | 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_SCALAR | AVX10.1 or 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 |
More AVX instructions
- VMOVHPS
- VMOVLHPS
- VMOVLPD
- VMOVLPS
- VMOVMSKPD
- VMOVMSKPS
- VMOVNTDQ
- VMOVNTDQA
- VMOVNTPD
- VMOVNTPS
- VMOVQ
- VMOVSD
- VMOVSHDUP
- VMOVSLDUP
- VMOVSS
- VMOVUPD
- VMOVUPS
- VMPSADBW
- VMULPD
- VMULPS
- VMULSS
- VORPD
- VORPS
- VPABSB
- VPABSD
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
- VPADDD
- VPADDQ
- VPADDSB
- VPADDSW
- VPADDUSB
- VPADDUSW
- VPADDW
- VPALIGNR
- VPAND
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 2B, page 4-148 (MULSD)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- 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.