Instruction
VFMADD231SS
Fused multiply-add of the low singles: second times third plus first, into the first; the rest is unchanged.
VFMADD231SS computes op2 × op3 + op1 for the low single and rounds once: the accumulator form of VFMADD231PS, whose page explains the three digits and the single rounding. Singles 1 to 3 of the destination keep their values and bits 511:128 are cleared, so the upper singles come from op1, the register that is both a source and the destination. The VEX form needs the FMA extension, the EVEX form AVX-512F or AVX10.1; the EVEX form exists only for xmm registers and takes a rounding mode in the instruction there, where the packed forms need 512-bit registers for one. VFMADD231SD is the double form.
From C
In our builds at -O2 with -march=x86-64-v3 or -v4, GCC 14 compiles
the loop s = fmaf(x[i], y[i], s) over float arrays to VFMADD231SS, s
in a register and y[i] from memory. Clang 23 unrolls it by eight: two
VFMADD231SS, then VFMADD132SS steps that write
each new sum into the register just loaded with x[i], so the sum moves
between two registers without a copy. Without the FMA extension, at the
x86-64 baseline or -v2, fmaf stays a call to the C library.
A plain a * b + c is fused as the contraction setting allows: GCC
fuses it in its default GNU C mode, not with -std=c17 or
-ffp-contract=off; Clang within one expression, also with -std=c17,
not with -ffp-contract=off.
Masking acts on the low single only. _mm_mask3_fmadd_ss(a, b, c, k)
keeps c’s low single where bit 0 of k is clear, so c must be the
destination: with -march=x86-64-v4 both compilers emit vfmadd231ss xmm2{k1}, xmm0, xmm1 and a VMOVAPS of the result.
Recorded on Zen 5
- Infinity × 0 plus the quiet NaN 7FC12345H, in
vfmadd231ss xmm7, xmm11, dword ptr [mem]under MXCSR 7F80H, returned that NaN and set no IE, as Intel’s table of FMA results (Volume 1, Table 14-17) has it for a quiet NaN addend. vfmadd231ss xmm7{k7}, xmm12, xmm7, {rn-sae}, with signaling NaNs in op1 and op3 and invalid unmasked (MXCSR 6600H), returned the quiet NaN 7FC12345H without a fault.
AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows alike a latency of 4 cycles, two per cycle on pipes FP0 and FP1.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VFMADD231SS xmm, xmm, m32
VFMADD231SS_XMMdq_XMMd_MEMd | VEX.LIG.66.0F38.W0 B9 /r | FMA + AVX |
VFMADD231SS xmm, xmm, xmm
VFMADD231SS_XMMdq_XMMd_XMMd | VEX.LIG.66.0F38.W0 B9 /r | FMA + AVX |
VFMADD231SS xmm {k}{z}, xmm, xmm, {er}
VFMADD231SS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.LIG.66.0F38.W0 B9 /r | AVX10.1 or AVX512F |
VFMADD231SS xmm {k}{z}, xmm, m32
VFMADD231SS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512 | EVEX.LIG.66.0F38.W0 B9 /r | AVX10.1 or AVX512F |
Latency and throughput
| Model | xmm, xmm, m32xmm {k}{z}, xmm, m32 | xmm, xmm, xmmxmm {k}{z}, xmm, xmm, {er} |
|---|---|---|
| Haswell, Broadwell | 10 / 0.5p01 | 5 / 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 | 10 / 2V0 V1 | 4 / 2V0 V1 |
| Piledriver | 10 / 1.5FPFMA FPU0 FPU1 | 5 / 1.5FPFMA FPU0 FPU1 FPU2 FPU3 |
| Zen, Zen 2 | 12 / 0.5FPU0 FPU1 | 5 / 0.5FPU0 FPU1 |
| Zen 3 | 11 / 0.5FP0 FP1 | 4 / 0.5FP0 FP1 |
| Zen 4 | 11 / 1FP0 FP1 | 4 / 11FP0 FP1 |
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 single: with bit 0 clear it keeps its old value, or is zeroed with {z}.
Result single 0 is computed from single 0 of xmm1, xmm2 and xmm3; singles 3 to 1 are those of xmm1. Result singles 3 to 0: a3, a2, a1, r0.
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 = xmm1.f32[0]
b = xmm2.f32[0]
c = src3.f32[0]
xmm1.f32[0] = fmadd(b, c, a)
elif zeroing:
xmm1.f32[0] = 0
# else: xmm1.f32[0] keeps its value
# xmm1.d[1] to [3] keep their values
# {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 |
|---|---|---|
VFMADD231SS xmm, xmm, xmm/m32 | ||
xmm | explicit | read, write |
xmm | explicit | read |
xmm/m32 | explicit | read |
VFMADD231SS xmm {k}{z}, xmm, xmm/m32, {er} | ||
xmm | explicit | read, write (masked) |
{k} | explicit | read (write mask) |
xmm | explicit | read |
xmm/m32 | 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 VFMADD231SS, 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_mask3_fmadd_round_ss
__m128 _mm_mask3_fmadd_round_ss(__m128 W, __m128 X, __m128 Y, __mmask8 U, const int R) |
|
_mm_mask3_fmadd_ss
__m128 _mm_mask3_fmadd_ss(__m128 __W, __m128 __X, __m128 __Y, __mmask8 __U) |
|
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 |
|---|---|---|
FMA | FMA + AVX XED and Intel’s SDM differ: XED also asks for the AVX bit, Sources: Intel XED v2026.08.23, datafiles/hswavx/cpuid.xed.txt; Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026), VFMADD132PD/VFMADD213PD/VFMADD231PD and the other FMA instructions: the opcode tables, from page 5-207; Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026), section 14.5.3, Detection of FMA, page 14-24. | 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, 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 FMA instructions
- VFMADD132PD
- VFMADD132PS
- VFMADD132SD
- VFMADD132SS
- VFMADD213PD
- VFMADD213PS
- VFMADD213SD
- VFMADD213SS
- VFMADD231PD
- VFMADD231PS
- VFMADD231SD
- VFMADDSUB132PD
- VFMADDSUB132PS
- VFMADDSUB213PD
- VFMADDSUB213PS
- VFMADDSUB231PD
- VFMADDSUB231PS
- VFMSUB132PD
- VFMSUB132PS
- VFMSUB132SD
- VFMSUB132SS
- VFMSUB213PD
- VFMSUB213PS
- VFMSUB213SD
- VFMSUB213SS
- VFMSUB231PD
- VFMSUB231PS
- VFMSUB231SD
- VFMSUB231SS
- VFMSUBADD132PD
- VFMSUBADD132PS
- VFMSUBADD213PD
- VFMSUBADD213PS
- VFMSUBADD231PD
- VFMSUBADD231PS
- VFNMADD132PD
- VFNMADD132PS
- VFNMADD132SD
- VFNMADD132SS
- VFNMADD213PD
More AVX10.1 instructions
- VFIXUPIMMPS
- VFIXUPIMMSD
- VFIXUPIMMSS
- VFMADD132PD
- VFMADD132PH
- VFMADD132PS
- VFMADD132SD
- VFMADD132SH
- VFMADD132SS
- VFMADD213PD
- VFMADD213PH
- VFMADD213PS
- VFMADD213SD
- VFMADD213SH
- VFMADD213SS
- VFMADD231PD
- VFMADD231PH
- VFMADD231PS
- VFMADD231SD
- VFMADD231SH
- VFMADDCPH
- VFMADDCSH
- VFMADDSUB132PD
- VFMADDSUB132PH
- VFMADDSUB132PS
- VFMADDSUB213PD
- VFMADDSUB213PH
- VFMADDSUB213PS
- VFMADDSUB231PD
- VFMADDSUB231PH
- VFMADDSUB231PS
- VFMSUB132PD
- VFMSUB132PH
- VFMSUB132PS
- VFMSUB132SD
- VFMSUB132SH
- VFMSUB132SS
- VFMSUB213PD
- VFMSUB213PH
- VFMSUB213PS
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 2C, page 5-232 (VFMADD132SS/
VFMADD213SS/ VFMADD231SS) - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 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.