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

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

Every encoding of VMULPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMULPS xmm, xmm, m128 VMULPS_XMMdq_XMMdq_MEMdqVEX.128.NP.0F.WIG 59 /rAVX
VMULPS xmm, xmm, xmm VMULPS_XMMdq_XMMdq_XMMdqVEX.128.NP.0F.WIG 59 /rAVX
VMULPS ymm, ymm, m256 VMULPS_YMMqq_YMMqq_MEMqqVEX.256.NP.0F.WIG 59 /rAVX
VMULPS ymm, ymm, ymm VMULPS_YMMqq_YMMqq_YMMqqVEX.256.NP.0F.WIG 59 /rAVX
VMULPS zmm {k}{z}, zmm, zmm, {er} VMULPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.NP.0F.W0 59 /rAVX10.1 or AVX512F
VMULPS zmm {k}{z}, zmm, m512/m32bcst VMULPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512EVEX.512.NP.0F.W0 59 /rAVX10.1 or AVX512F
VMULPS xmm {k}{z}, xmm, xmm VMULPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.NP.0F.W0 59 /rAVX10.1 or AVX512F + AVX512VL
VMULPS xmm {k}{z}, xmm, m128/m32bcst VMULPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.128.NP.0F.W0 59 /rAVX10.1 or AVX512F + AVX512VL
VMULPS ymm {k}{z}, ymm, ymm VMULPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.NP.0F.W0 59 /rAVX10.1 or AVX512F + AVX512VL
VMULPS ymm {k}{z}, ymm, m256/m32bcst VMULPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512EVEX.256.NP.0F.W0 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/m32bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m32bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmm, {er}zmm {k}{z}, zmm, m512/m32bcst
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
Zen10 / 0.5FPU0 FPU13 / 0.5FPU0 FPU110 / 1FPU0 FPU13 / 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
Jaguar7 / 1FPM FPU12 / 1FPM FPU17 / 2FPM FPU12 / 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.

Element-wise: each single of the result comes from the single in the same place in each source.
VMULPS: element by elementResult 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.0123xmm2a1110k1a0×b0a1×b1a3×b3xmm10123xmm3or m128b

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 up

Run on AMD Zen 5 (EPYC 9645): 15 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
VMULPS xmm, xmm, xmm/m128 VMULPS ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
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, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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.

IntrinsicCompiles to
_mm_mul_ps __m128 _mm_mul_ps(__m128 __a, __m128 __b)

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

_mm_mask_mul_ps __m128 _mm_mask_mul_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B)

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

_mm_maskz_mul_ps __m128 _mm_maskz_mul_ps(__mmask8 __U, __m128 __A, __m128 __B)

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

_mm256_mul_ps __m256 _mm256_mul_ps(__m256 __a, __m256 __b)

VMULPS ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_mul_ps __m256 _mm256_mask_mul_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B)

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

_mm256_maskz_mul_ps __m256 _mm256_maskz_mul_ps(__mmask8 __U, __m256 __A, __m256 __B)

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

_mm512_mul_ps __m512 _mm512_mul_ps(__m512 __a, __m512 __b)

VMULPS zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mul_round_ps __m512 _mm512_mul_round_ps(__m512 A, __m512 B, const int R)

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

_mm512_mask_mul_ps __m512 _mm512_mask_mul_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B)

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

_mm512_mask_mul_round_ps __m512 _mm512_mask_mul_round_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int R)

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

_mm512_maskz_mul_ps __m512 _mm512_maskz_mul_ps(__mmask16 __U, __m512 __A, __m512 __B)

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

_mm512_maskz_mul_round_ps __m512 _mm512_maskz_mul_round_ps(__mmask16 U, __m512 A, __m512 B, const int R)

VMULPS 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-145 (MULPS)
  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.