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

VMULSS is MULSS in VEX and EVEX encodings: the product of the low singles of its two sources, with singles 1 to 3 copied from the first source and the bits above 127 cleared. The MULSS page shows how constants and powf compile, and VADDSS what the encodings change. The VEX form needs AVX, the EVEX form AVX-512F or AVX10.1.

Where the FMA takes over

The levels x86-64-v3 and x86-64-v4 include FMA, and GCC 14 and Clang 23 contract a product that feeds a sum. So in our builds at -O2 with -march=x86-64-v3 or x86-64-v4, the dot product fa[0]*fb[0] + fa[1]*fb[1] + fa[2]*fb[2] over global arrays has a single VMULSS, for the product of the second pair, and adds the other two with VFMADD231SS, each rounding once. The x86-64 baseline computes three MULSS and two ADDSS, so the two builds can differ in the last bit. VMULSS remains where nothing is added to the product.

On Zen 5

  • vmulss xmm24{k7}{z}, xmm3, dword ptr [mem], with bit 0 of K7 set and MXCSR at FFC0H (FTZ and DAZ set), squared the smallest denormal and gave +0 with no flag: DAZ read it as zero. MULSS’s page squares a denormal with both clear, which sets UE, PE and DE, and cites AMD’s advice to set the two for speed.
  • vmulss xmm1, xmm2, xmm3, under 3FC0H, gave -0 for -0 times +0, while XMM2’s upper singles, signaling NaNs among them, came through unchanged without IE.
  • vmulss xmm12, xmm6, dword ptr [mem], under 7F80H, multiplied the quiet NaN 7FC00000H by FFC00000H and returned the first source’s NaN.

AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows 3 cycles on pipes FP0 and FP1, as for MULSS. VMULSD is the double form.

Forms

Every encoding of VMULSS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMULSS xmm, xmm, m32 VMULSS_XMMdq_XMMdq_MEMdVEX.LIG.F3.0F.WIG 59 /rAVX
VMULSS xmm, xmm, xmm VMULSS_XMMdq_XMMdq_XMMdVEX.LIG.F3.0F.WIG 59 /rAVX
VMULSS xmm {k}{z}, xmm, xmm, {er} VMULSS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.LIG.F3.0F.W0 59 /rAVX10.1 or AVX512F
VMULSS xmm {k}{z}, xmm, m32 VMULSS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.LIG.F3.0F.W0 59 /rAVX10.1 or AVX512F

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, m32
xmm {k}{z}, xmm, m32
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm, {er}
Sandy Bridge11 / 1p05 / 1p0
Haswell10 / 0.5p015 / 0.5p01
Broadwell8 / 0.5p013 / 0.5p01
Skylake, Skylake-SP, Ice Lake9 / 0.5p014 / 0.5p01
Alder Lake, Sapphire Rapids11 / 0.5p014 / 0.5p01
Lunar Lake9 / 2V0 V13 / 1.5V0 V1
Piledriver10 / 1.5FPFMA FPU15 / 1FPFMA FPU1
Zen, Zen 210 / 0.5FPU0 FPU13 / 0.5FPU0 FPU1
Zen 3, Zen 410 / 0.5FP0 FP13 / 0.5FP0 FP1
Jaguar7 / 1FPM FPU12 / 1FPM 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.

Scalar: only the low single is computed; the other singles come from xmm2.
VMULSS: the low elementResult single 0 is computed from single 0 of xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, a1, a0×b0.0123xmm2a1k1a0×b0a1a2a3xmm10123xmm3or m32b

The write mask k1 applies to the low single: with bit 0 clear it keeps its old value, or is zeroed with {z}.

Result single 0 is computed from single 0 of xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, 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.f32[0]
    b = src3.f32[0]
    xmm1.f32[0] = mul(a, b)
elif zeroing:
    xmm1.f32[0] = 0
# else: xmm1.f32[0] keeps its value
for i in range(1, 4):
    xmm1.d[i] = xmm2.d[i]
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 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
VMULSS xmm, xmm, xmm/m32
xmmexplicitwrite
xmmexplicitread
xmm/m32explicitread
VMULSS xmm {k}{z}, xmm, xmm/m32, {er}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m32explicitread

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 VMULSS, 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_round_ss __m128 _mm_mul_round_ss(__m128 A, __m128 B, const int R)

VMULSS xmm, xmm, xmm, {er} EVEX.LIG -mavx512f

_mm_mul_ss __m128 _mm_mul_ss(__m128 __a, __m128 __b)

VMULSS xmm, xmm, xmm VEX.LIG -mavxwith AVX enabled

_mm_mask_mul_round_ss __m128 _mm_mask_mul_round_ss(__m128 W, __mmask8 U, __m128 A, __m128 B, const int R)

VMULSS xmm {k}, xmm, xmm, {er} EVEX.LIG -mavx512f

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

VMULSS xmm {k}, xmm, xmm EVEX.LIG -mavx512f

_mm_maskz_mul_round_ss __m128 _mm_maskz_mul_round_ss(__mmask8 U, __m128 A, __m128 B, const int R)

VMULSS xmm {k}{z}, xmm, xmm, {er} EVEX.LIG -mavx512f

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

VMULSS xmm {k}{z}, xmm, xmm EVEX.LIG -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.

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-150 (MULSS)
  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.