Instruction
VFNMADD231PS
Fused negated multiply-add of packed singles: minus second operand times third, plus first, into the first.
VFNMADD231PS computes op1 - op2 × op3 for each single, rounded once:
the product is negated, not the sum. It is the subtracting twin of
VFMADD231PS, whose page explains the three
digits, the masking and the {er} rounding of the EVEX forms. The
four FMA families differ only in two signs:
| Family | Computes |
|---|---|
| VFMADD231PS | x × y + z |
| VFMSUB231PS | x × y - z |
| VFNMADD231PS | -(x × y) + z |
| VFNMSUB231PS | -(x × y) - z |
What it is for
z - x × y in one rounding is the residual of numerical code: the
error of a quotient, a - q × b, or the step of Newton’s method for a
reciprocal, 1 - x × r, both exact as long as the result is
representable. In our builds at -O2 with -march=x86-64-v3, the loop
acc[i] -= x[i] * y[i] over floats becomes VFNMADD213PS in Clang 23,
with acc[i] from memory, and VFNMADD132PS in GCC 14. The 231 form
appears when the sum stays in a register: with -ffast-math, GCC
compiles s -= x[i] * y[i] to VFNMADD231PS on zmm registers for
-march=x86-64-v4, while Clang multiplies one pair with VMULPS, folds
the next in with VFNMSUB231PS, -(x × y) - p, and adds that to its sums.
Signs on Zen 5
The negation applies to numbers, not to NaNs, as Intel’s table of FMA results lists (Volume 1, Table 14-17). In the recorded cases:
- the quiet NaN 7FC12345H as a factor came back as 7FC12345H, its sign bit still clear, in preference to the addend FFC00005H;
- infinity × 0 with the addend 7FC12345H returned that addend, not the default NaN FFC00000H, which the same product gave with the addend 1;
- under
{rz-sae}, -(10^-30 × 10^-30) + 0 gave -0: the exact result is a tiny negative number, and rounding it toward zero keeps its sign.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VFNMADD231PS xmm, xmm, m128
VFNMADD231PS_XMMdq_XMMdq_MEMdq | VEX.128.66.0F38.W0 BC /r | FMA + AVX |
VFNMADD231PS xmm, xmm, xmm
VFNMADD231PS_XMMdq_XMMdq_XMMdq | VEX.128.66.0F38.W0 BC /r | FMA + AVX |
VFNMADD231PS ymm, ymm, m256
VFNMADD231PS_YMMqq_YMMqq_MEMqq | VEX.256.66.0F38.W0 BC /r | FMA + AVX |
VFNMADD231PS ymm, ymm, ymm
VFNMADD231PS_YMMqq_YMMqq_YMMqq | VEX.256.66.0F38.W0 BC /r | FMA + AVX |
VFNMADD231PS zmm {k}{z}, zmm, zmm, {er}
VFNMADD231PS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512 | EVEX.512.66.0F38.W0 BC /r | AVX10.1 or AVX512F |
VFNMADD231PS zmm {k}{z}, zmm, m512/m32bcst
VFNMADD231PS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512 | EVEX.512.66.0F38.W0 BC /r | AVX10.1 or AVX512F |
VFNMADD231PS xmm {k}{z}, xmm, xmm
VFNMADD231PS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.128.66.0F38.W0 BC /r | AVX10.1 or AVX512F + AVX512VL |
VFNMADD231PS xmm {k}{z}, xmm, m128/m32bcst
VFNMADD231PS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512 | EVEX.128.66.0F38.W0 BC /r | AVX10.1 or AVX512F + AVX512VL |
VFNMADD231PS ymm {k}{z}, ymm, ymm
VFNMADD231PS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512 | EVEX.256.66.0F38.W0 BC /r | AVX10.1 or AVX512F + AVX512VL |
VFNMADD231PS ymm {k}{z}, ymm, m256/m32bcst
VFNMADD231PS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512 | EVEX.256.66.0F38.W0 BC /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 |
|---|---|---|---|---|---|---|
| Haswell | 11 / 0.5p01 | 5 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p01 | ||
| Broadwell | 10 / 0.5p01 | 5 / 0.5p01 | 11 / 0.5p01 | 5 / 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 | 10 / 2V0 V1 | 4 / 2V0 V1 | 11 / 2.33V0 V1 | 4 / 2V0 V1 | ||
| Piledriver | 10 / 1.5FPFMA FPU0 FPU1 | 5 / 1.5FPFMA FPU0 FPU1 FPU2 FPU3 | 10 / 1.5FPFMA FPU0 FPU1 | 5 / 1.5FPFMA FPU0 FPU1 FPU2 FPU3 | ||
| Zen | 12 / 0.5FPU0 FPU1 | 5 / 0.5FPU0 FPU1 | 12 / 1FPU0 FPU1 | 5 / 1FPU0 FPU1 | ||
| Zen 2 | 12 / 0.5FPU0 FPU1 | 5 / 0.5FPU0 FPU1 | 12 / 0.5FPU0 FPU1 | 5 / 0.5FPU0 FPU1 | ||
| Zen 3 | 11 / 0.5FP0 FP1 | 4 / 0.5FP0 FP1 | 11 / 0.5FP0 FP1 | 4 / 0.5FP0 FP1 | ||
| Zen 4 | 11 / 0.5FP0 FP1 | 4 / 0.5FP0 FP1 | 11 / 0.5FP0 FP1 | 4 / 0.5FP0 FP1 | 4 / 1FP0 FP1 | 11 / 1FP0 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.
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. The sources are drawn above the result, each element in its own column.
Result single i comes from single i of xmm1, xmm2 and xmm3. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.
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 = zmm1.f32[i]
b = zmm2.f32[i]
c = src3.f32[i]
zmm1.f32[i] = fnmadd(b, c, a)
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 |
|---|---|---|
VFNMADD231PS xmm, xmm, xmm/m128 VFNMADD231PS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | read, write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VFNMADD231PS xmm {k}{z}, xmm, xmm/m128/m32bcst VFNMADD231PS ymm {k}{z}, ymm, ymm/m256/m32bcst VFNMADD231PS zmm {k}{z}, zmm, zmm/m512/m32bcst, {er} | ||
xmm, ymm, zmm | explicit | read, 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 VFNMADD231PS, 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_fnmadd_ps
__m128 _mm_fnmadd_ps(__m128 __A, __m128 __B, __m128 __C) |
Clang's comment misspells the instruction as VFNMADD213DPS; Clang emits VFNMADD213PS. |
_mm_mask3_fnmadd_ps
__m128 _mm_mask3_fnmadd_ps(__m128 __A, __m128 __B, __m128 __C, __mmask8 __U) |
|
_mm_maskz_fnmadd_ps
__m128 _mm_maskz_fnmadd_ps(__mmask8 __U, __m128 __A, __m128 __B, __m128 __C) |
|
_mm256_fnmadd_ps
__m256 _mm256_fnmadd_ps(__m256 __A, __m256 __B, __m256 __C) |
|
_mm256_mask3_fnmadd_ps
__m256 _mm256_mask3_fnmadd_ps(__m256 __A, __m256 __B, __m256 __C, __mmask8 __U) |
|
_mm256_maskz_fnmadd_ps
__m256 _mm256_maskz_fnmadd_ps(__mmask8 __U, __m256 __A, __m256 __B, __m256 __C) |
|
_mm512_fnmadd_ps
__m512 _mm512_fnmadd_ps(__m512 __A, __m512 __B, __m512 __C) |
|
_mm512_fnmadd_round_ps
__m512 _mm512_fnmadd_round_ps(__m512 A, __m512 B, __m512 C, const int R) |
|
_mm512_mask3_fnmadd_ps
__m512 _mm512_mask3_fnmadd_ps(__m512 __A, __m512 __B, __m512 __C, __mmask16 __U) |
|
_mm512_mask3_fnmadd_round_ps
__m512 _mm512_mask3_fnmadd_round_ps(__m512 A, __m512 B, __m512 C, __mmask16 U, const int R) |
|
_mm512_maskz_fnmadd_ps
__m512 _mm512_maskz_fnmadd_ps(__mmask16 __U, __m512 __A, __m512 __B, __m512 __C) |
|
_mm512_maskz_fnmadd_round_ps
__m512 _mm512_maskz_fnmadd_round_ps(__mmask16 U, __m512 A, __m512 B, __m512 C, 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.
| 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_512 | 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 |
AVX512F_128 | AVX10.1 or AVX512F + 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_128 | Same as AVX512F_128 |
More FMA instructions
- VFMSUB132PS
- VFMSUB132SD
- VFMSUB132SS
- VFMSUB213PD
- VFMSUB213PS
- VFMSUB213SD
- VFMSUB213SS
- VFMSUB231PD
- VFMSUB231PS
- VFMSUB231SD
- VFMSUB231SS
- VFMSUBADD132PD
- VFMSUBADD132PS
- VFMSUBADD213PD
- VFMSUBADD213PS
- VFMSUBADD231PD
- VFMSUBADD231PS
- VFNMADD132PD
- VFNMADD132PS
- VFNMADD132SD
- VFNMADD132SS
- VFNMADD213PD
- VFNMADD213PS
- VFNMADD213SD
- VFNMADD213SS
- VFNMADD231PD
- VFNMADD231SD
- VFNMADD231SS
- VFNMSUB132PD
- VFNMSUB132PS
- VFNMSUB132SD
- VFNMSUB132SS
- VFNMSUB213PD
- VFNMSUB213PS
- VFNMSUB213SD
- VFNMSUB213SS
- VFNMSUB231PD
- VFNMSUB231PS
- VFNMSUB231SD
- VFNMSUB231SS
More AVX10.1 instructions
- VFMSUBADD213PS
- VFMSUBADD231PD
- VFMSUBADD231PH
- VFMSUBADD231PS
- VFMULCPH
- VFMULCSH
- VFNMADD132PD
- VFNMADD132PH
- VFNMADD132PS
- VFNMADD132SD
- VFNMADD132SH
- VFNMADD132SS
- VFNMADD213PD
- VFNMADD213PH
- VFNMADD213PS
- VFNMADD213SD
- VFNMADD213SH
- VFNMADD213SS
- VFNMADD231PD
- VFNMADD231PH
- VFNMADD231SD
- VFNMADD231SH
- VFNMADD231SS
- VFNMSUB132PD
- VFNMSUB132PH
- VFNMSUB132PS
- VFNMSUB132SD
- VFNMSUB132SH
- VFNMSUB132SS
- VFNMSUB213PD
- VFNMSUB213PH
- VFNMSUB213PS
- VFNMSUB213SD
- VFNMSUB213SH
- VFNMSUB213SS
- VFNMSUB231PD
- VFNMSUB231PH
- VFNMSUB231PS
- VFNMSUB231SD
- VFNMSUB231SH
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-312 (VFNMADD132PS/
VFNMADD213PS/ VFNMADD231PS) - 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)
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.