Instruction
VFNMSUB132PS
Fused negated multiply-subtract of packed singles: minus first operand times third, minus second, into the first.
VFNMSUB132PS computes -(op1 × op3) - op2 for each single, rounded once: the product of the destination and the operand that may come from memory, negated, minus the middle register. VFNMSUB231PS covers the doubly negated family and why it is not a VFMADD with its result negated, and VFMADD132PS the operand roles of the 132 form. The VEX forms need the FMA extension; the EVEX forms need AVX-512F (with AVX512VL below 512 bits) or AVX10.1 and add a write mask, a multiplier of one single broadcast from memory and, in the 512-bit register form, a rounding mode given in the instruction.
In our builds
At -O2 over fixed-size float arrays, GCC 14 compiles
a[i] = -(b[i] * c[i]) - d[i] and a[i] = -(b[i] * c[i]) - a[i] to
VFNMSUB132PS with b[i] from memory, on ymm registers for
-march=x86-64-v3 and zmm for -v4, with or without -ffast-math.
Clang 23 uses VFNMSUB213PS for both.
Recorded on Zen 5
vfnmsub132ps ymm4, ymm4, ymm4 computes -(x × x) - x. Under MXCSR
DF80H (round up, FTZ):
- x = +0 gave -0: the negated product, -0, minus +0 is a sum of two negative zeros;
- x = 10^-30 gave -x itself, 8DA24260H, as rounding up drops the tiny product, where VFNMSUB231PS rounding down returned the single below;
- x = 10^30 gave the most negative finite single, not minus infinity, since rounding up stops a negative overflow there. OE and PE were set.
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 |
|---|---|---|
VFNMSUB132PS xmm, xmm, m128
VFNMSUB132PS_XMMdq_XMMdq_MEMdq | VEX.128.66.0F38.W0 9E /r | FMA + AVX |
VFNMSUB132PS xmm, xmm, xmm
VFNMSUB132PS_XMMdq_XMMdq_XMMdq | VEX.128.66.0F38.W0 9E /r | FMA + AVX |
VFNMSUB132PS ymm, ymm, m256
VFNMSUB132PS_YMMqq_YMMqq_MEMqq | VEX.256.66.0F38.W0 9E /r | FMA + AVX |
VFNMSUB132PS ymm, ymm, ymm
VFNMSUB132PS_YMMqq_YMMqq_YMMqq | VEX.256.66.0F38.W0 9E /r | FMA + AVX |
VFNMSUB132PS zmm {k}{z}, zmm, zmm, {er}
VFNMSUB132PS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512 | EVEX.512.66.0F38.W0 9E /r | AVX10.1 or AVX512F |
VFNMSUB132PS zmm {k}{z}, zmm, m512/m32bcst
VFNMSUB132PS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512 | EVEX.512.66.0F38.W0 9E /r | AVX10.1 or AVX512F |
VFNMSUB132PS xmm {k}{z}, xmm, xmm
VFNMSUB132PS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.128.66.0F38.W0 9E /r | AVX10.1 or AVX512F + AVX512VL |
VFNMSUB132PS xmm {k}{z}, xmm, m128/m32bcst
VFNMSUB132PS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512 | EVEX.128.66.0F38.W0 9E /r | AVX10.1 or AVX512F + AVX512VL |
VFNMSUB132PS ymm {k}{z}, ymm, ymm
VFNMSUB132PS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512 | EVEX.256.66.0F38.W0 9E /r | AVX10.1 or AVX512F + AVX512VL |
VFNMSUB132PS ymm {k}{z}, ymm, m256/m32bcst
VFNMSUB132PS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512 | EVEX.256.66.0F38.W0 9E /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] = fnmsub(a, c, 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 |
|---|---|---|
VFNMSUB132PS xmm, xmm, xmm/m128 VFNMSUB132PS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | read, write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VFNMSUB132PS xmm {k}{z}, xmm, xmm/m128/m32bcst VFNMSUB132PS ymm {k}{z}, ymm, ymm/m256/m32bcst VFNMSUB132PS 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 VFNMSUB132PS, 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_fnmsub_ps
__m128 _mm_fnmsub_ps(__m128 __A, __m128 __B, __m128 __C) |
|
_mm_mask_fnmsub_ps
__m128 _mm_mask_fnmsub_ps(__m128 __A, __mmask8 __U, __m128 __B, __m128 __C) |
|
_mm_maskz_fnmsub_ps
__m128 _mm_maskz_fnmsub_ps(__mmask8 __U, __m128 __A, __m128 __B, __m128 __C) |
|
_mm256_fnmsub_ps
__m256 _mm256_fnmsub_ps(__m256 __A, __m256 __B, __m256 __C) |
|
_mm256_mask_fnmsub_ps
__m256 _mm256_mask_fnmsub_ps(__m256 __A, __mmask8 __U, __m256 __B, __m256 __C) |
|
_mm256_maskz_fnmsub_ps
__m256 _mm256_maskz_fnmsub_ps(__mmask8 __U, __m256 __A, __m256 __B, __m256 __C) |
|
_mm512_fnmsub_ps
__m512 _mm512_fnmsub_ps(__m512 __A, __m512 __B, __m512 __C) |
|
_mm512_mask_fnmsub_ps
__m512 _mm512_mask_fnmsub_ps(__m512 __A, __mmask16 __U, __m512 __B, __m512 __C) |
|
_mm512_mask_fnmsub_round_ps
__m512 _mm512_mask_fnmsub_round_ps(__m512 A, __mmask16 U, __m512 B, __m512 C, const int R) |
|
_mm512_maskz_fnmsub_ps
__m512 _mm512_maskz_fnmsub_ps(__mmask16 __U, __m512 __A, __m512 __B, __m512 __C) |
|
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
- VFNMADD231PS
- VFNMADD231SD
- VFNMADD231SS
- VFNMSUB132PD
- VFNMSUB132SD
- VFNMSUB132SS
- VFNMSUB213PD
- VFNMSUB213PS
- VFNMSUB213SD
- VFNMSUB213SS
- VFNMSUB231PD
- VFNMSUB231PS
- VFNMSUB231SD
- VFNMSUB231SS
More AVX10.1 instructions
- VFNMADD132PD
- VFNMADD132PH
- VFNMADD132PS
- VFNMADD132SD
- VFNMADD132SH
- VFNMADD132SS
- VFNMADD213PD
- VFNMADD213PH
- VFNMADD213PS
- VFNMADD213SD
- VFNMADD213SH
- VFNMADD213SS
- VFNMADD231PD
- VFNMADD231PH
- VFNMADD231PS
- VFNMADD231SD
- VFNMADD231SH
- VFNMADD231SS
- VFNMSUB132PD
- VFNMSUB132PH
- VFNMSUB132SD
- VFNMSUB132SH
- VFNMSUB132SS
- VFNMSUB213PD
- VFNMSUB213PH
- VFNMSUB213PS
- VFNMSUB213SD
- VFNMSUB213SH
- VFNMSUB213SS
- VFNMSUB231PD
- VFNMSUB231PH
- VFNMSUB231PS
- VFNMSUB231SD
- VFNMSUB231SH
- VFNMSUB231SS
- VFPCLASSPD
- VFPCLASSPH
- VFPCLASSPS
- VFPCLASSSD
- VFPCLASSSH
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-332 (VFNMSUB132PS/
VFNMSUB213PS/ VFNMSUB231PS) - 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
- 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.