Instruction
VMULPS
Multiplies packed singles.
VMULPS is MULPS in VEX and EVEX encodings; the MULPS
page covers MXCSR, denormals and the FTZ and DAZ bits. The encodings
add what VADDPS shows: a separate destination, the
bits above the result cleared, and in EVEX a write mask, a broadcast
single and a rounding mode given in the instruction. Under {rn-sae},
with the underflow and invalid exceptions unmasked, Zen 5 multiplied the
smallest normal single by 0.5 to the denormal 2^-127 and quieted a
signaling NaN in another element, without #XM and without changing
MXCSR.
Contraction into FMA
What changes most in practice is that a multiplication followed by an
addition may not compile to VMULPS at all. The x86-64-v3 level includes
FMA, and a fused multiply-add rounds once where VMULPS and VADDPS round
twice. For a[i] = b[i] * c[i] + d[i] over floats, GCC 14 and Clang 23
at -O2 emit MULPS and ADDPS for the baseline, but one
VFMADD132PS (GCC) or
VFMADD213PS (Clang) per vector with
-march=x86-64-v3, so the two builds of the same source can differ in
the last bit. How far they go differs:
- GCC fuses by default, even across statements
(
t = b[i] * c[i]; a[i] = t + d[i];), but not with an ISO dialect such as-std=c17. - Clang fuses only within one expression, whatever the dialect: the two-statement version keeps VMULPS and VADDPS.
- With
-ffp-contract=off, both keep VMULPS and VADDPS.
Pipes on Zen 5
AMD’s Zen 5 guide lists VMULPS as one macro-op with a latency of 3 cycles at every width. It runs on pipes 0 and 1, which also do the fused multiply-adds, compares and variable blends, while additions go to pipes 2 and 3 (Section 2.11.1), so a loop with as many multiplications as additions can keep all four busy.
In the optimization guide
What the optimization guide says about VMULPS, 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
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VMULPS xmm, xmm, m128
VMULPS_XMMdq_XMMdq_MEMdq | VEX.128.NP.0F.WIG 59 /r | AVX |
VMULPS xmm, xmm, xmm
VMULPS_XMMdq_XMMdq_XMMdq | VEX.128.NP.0F.WIG 59 /r | AVX |
VMULPS ymm, ymm, m256
VMULPS_YMMqq_YMMqq_MEMqq | VEX.256.NP.0F.WIG 59 /r | AVX |
VMULPS ymm, ymm, ymm
VMULPS_YMMqq_YMMqq_YMMqq | VEX.256.NP.0F.WIG 59 /r | AVX |
VMULPS zmm {k}{z}, zmm, zmm, {er}
VMULPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512 | EVEX.512.NP.0F.W0 59 /r | AVX10.1 or AVX512F |
VMULPS zmm {k}{z}, zmm, m512/m32bcst
VMULPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512 | EVEX.512.NP.0F.W0 59 /r | AVX10.1 or AVX512F |
VMULPS xmm {k}{z}, xmm, xmm
VMULPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.128.NP.0F.W0 59 /r | AVX10.1 or AVX512F + AVX512VL |
VMULPS xmm {k}{z}, xmm, m128/m32bcst
VMULPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512 | EVEX.128.NP.0F.W0 59 /r | AVX10.1 or AVX512F + AVX512VL |
VMULPS ymm {k}{z}, ymm, ymm
VMULPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512 | EVEX.256.NP.0F.W0 59 /r | AVX10.1 or AVX512F + AVX512VL |
VMULPS ymm {k}{z}, ymm, m256/m32bcst
VMULPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512 | EVEX.256.NP.0F.W0 59 /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m32bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m32bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm, {er} | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|
| Sandy Bridge | 11 / 1p0 | 5 / 1p0 | 12 / 1p0 | 5 / 1p0 | ||
| Haswell | 11 / 0.5p01 | 5 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p01 | ||
| Broadwell | 8 / 0.5p01 | 3 / 0.5p01 | 9 / 0.5p01 | 3 / 0.5p01 | ||
| Skylake | 10 / 0.5p01 | 4 / 0.5p01 | 11 / 0.5p01 | 4 / 0.5p01 | ||
| Skylake-SP | 10 / 0.5p01 | 4 / 0.5p01 | 11 / 0.5p01 | 4 / 0.5p01 | 4 / 0.5p05 | 11 / 0.5p05 |
| Ice Lake | 10 / 0.5p01 | 4 / 0.5p01 | 11 / 0.5p01 | 4 / 0.5p01 | 4 / 1p0 | 11 / 1p0 |
| Alder Lake | 11 / 0.5p01 | 4 / 0.5p01 | 12 / 0.5p01 | 4 / 0.5p01 | ||
| Sapphire Rapids | 11 / 0.5p01 | 4 / 0.5p01 | 12 / 0.5p01 | 4 / 0.5p01 | 4 / 1p0 | 12 / 1p0 |
| Lunar Lake | 9 / 2V0 V1 | 3 / 1.5V0 V1 | 10 / 2.33V0 V1 | 3 / 1.5V0 V1 | ||
| Piledriver | 10 / 1.5FPFMA FPU1 | 5 / 1FPFMA FPU1 | 10 / 1.5FPFMA FPU1 | 5 / 1FPFMA FPU1 | ||
| Zen | 10 / 0.5FPU0 FPU1 | 3 / 0.5FPU0 FPU1 | 10 / 1FPU0 FPU1 | 3 / 1FPU0 FPU1 | ||
| Zen 2 | 10 / 0.5FPU0 FPU1 | 3 / 0.5FPU0 FPU1 | 10 / 0.5FPU0 FPU1 | 3 / 0.5FPU0 FPU1 | ||
| Zen 3 | 10 / 0.5FP0 FP1 | 3 / 0.5FP0 FP1 | 10 / 0.5FP0 FP1 | 3 / 0.5FP0 FP1 | ||
| Zen 4 | 10 / 0.5FP0 FP1 | 3 / 0.5FP0 FP1 | 10 / 0.5FP0 FP1 | 3 / 0.5FP0 FP1 | 3 / 1FP0 FP1 | 10 / 1FP0 FP1 |
| Jaguar | 7 / 1FPM FPU1 | 2 / 1FPM FPU1 | 7 / 2FPM FPU1 | 2 / 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.
Every single works alike: 4, 8 and 16 singles 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 m32bcst, one single from memory stands for every element of the last source.
Result single i comes from single i of xmm2 and xmm3. Result singles 3 to 0: a3×b3, unchanged (bit 2 of k1 is 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 // 32):
if k1[i]: # 1 without a write mask
a = zmm2.f32[i]
b = src3.f32[i]
zmm1.f32[i] = mul(a, b)
elif zeroing:
zmm1.f32[i] = 0
# else: zmm1.f32[i] keeps its value
# m32bcst: src3.f32[i] is the m32 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 15 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VMULPS xmm, xmm, xmm/m128 VMULPS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VMULPS xmm {k}{z}, xmm, xmm/m128/m32bcst VMULPS ymm {k}{z}, ymm, ymm/m256/m32bcst VMULPS zmm {k}{z}, zmm, zmm/m512/m32bcst, {er} | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | 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-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 VMULPS, 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_ps
__m128 _mm_mul_ps(__m128 __a, __m128 __b) |
|
_mm_mask_mul_ps
__m128 _mm_mask_mul_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B) |
|
_mm_maskz_mul_ps
__m128 _mm_maskz_mul_ps(__mmask8 __U, __m128 __A, __m128 __B) |
|
_mm256_mul_ps
__m256 _mm256_mul_ps(__m256 __a, __m256 __b) |
|
_mm256_mask_mul_ps
__m256 _mm256_mask_mul_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B) |
|
_mm256_maskz_mul_ps
__m256 _mm256_maskz_mul_ps(__mmask8 __U, __m256 __A, __m256 __B) |
|
_mm512_mul_ps
__m512 _mm512_mul_ps(__m512 __a, __m512 __b) |
|
_mm512_mul_round_ps
__m512 _mm512_mul_round_ps(__m512 A, __m512 B, const int R) |
|
_mm512_mask_mul_ps
__m512 _mm512_mask_mul_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_mask_mul_round_ps
__m512 _mm512_mask_mul_round_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int R) |
|
_mm512_maskz_mul_ps
__m512 _mm512_maskz_mul_ps(__mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_maskz_mul_round_ps
__m512 _mm512_maskz_mul_round_ps(__mmask16 U, __m512 A, __m512 B, const int R) |
|
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 AVX instructions
- VMOVHPD
- VMOVHPS
- VMOVLHPS
- VMOVLPD
- VMOVLPS
- VMOVMSKPD
- VMOVMSKPS
- VMOVNTDQ
- VMOVNTDQA
- VMOVNTPD
- VMOVNTPS
- VMOVQ
- VMOVSD
- VMOVSHDUP
- VMOVSLDUP
- VMOVSS
- VMOVUPD
- VMOVUPS
- VMPSADBW
- VMULPD
- VMULSD
- VMULSS
- VORPD
- VORPS
- VPABSB
- VPABSD
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
- VPADDD
- VPADDQ
- VPADDSB
- VPADDSW
- VPADDUSB
- VPADDUSW
- VPADDW
- VPALIGNR
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-145 (MULPS)
- 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.