Instruction
VFNMADD132PD
Fused negated multiply-add of packed doubles: minus first operand times third, plus second, into the first.
VFNMADD132PD computes -(op1 × op3) + op2 for each double, rounded once: the product of the destination and the operand that may come from memory is subtracted from the middle register. It is the double form of VFNMADD132PS; VFNMADD231PS covers the negated family, its uses and the signs of its NaNs. 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 double broadcast from memory and, in the 512-bit register form, a rounding mode given in the instruction.
In our builds
At -O2 over double arrays, with -march=x86-64-v3 (ymm) and -v4
(zmm), GCC 14 uses VFNMADD132PD for w[i] = z[i] - x[i] * y[i] and
w[i] -= x[i] * y[i], with y[i] from memory, and three VFNMADD132PD
for the polynomial 2 - (1 - (0.5 - 0.25 * t) * t) * t with
t = x[i], loading t once and keeping it in a register. Clang 23
uses VFNMADD213PD for all three.
Rounding on Zen 5
vfnmadd132pd ymm1{k6}{z}, ymm2, ymm3under MXCSR BF80H (round down, FTZ) computed -(10^300 × 10^300) + (-10^300) as minus infinity in element 2 and zeroed the rest. Under 7F80H (toward zero),vfnmadd132pd ymm1, ymm2, ymmword ptr [mem]turned the same values into the most negative finite double, FFEFFFFFFFFFFFFFH. Both set OE and PE.- Under DF80H (round up, FTZ),
vfnmadd132pd ymm0, ymm13, ymm9gave -0 for -(2^-1074 × 1) + 0: FTZ flushes the tiny negative result to a zero of its sign. It set DE, UE and PE.
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 |
|---|---|---|
VFNMADD132PD xmm, xmm, m128
VFNMADD132PD_XMMdq_XMMdq_MEMdq | VEX.128.66.0F38.W1 9C /r | FMA + AVX |
VFNMADD132PD xmm, xmm, xmm
VFNMADD132PD_XMMdq_XMMdq_XMMdq | VEX.128.66.0F38.W1 9C /r | FMA + AVX |
VFNMADD132PD ymm, ymm, m256
VFNMADD132PD_YMMqq_YMMqq_MEMqq | VEX.256.66.0F38.W1 9C /r | FMA + AVX |
VFNMADD132PD ymm, ymm, ymm
VFNMADD132PD_YMMqq_YMMqq_YMMqq | VEX.256.66.0F38.W1 9C /r | FMA + AVX |
VFNMADD132PD zmm {k}{z}, zmm, zmm, {er}
VFNMADD132PD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512 | EVEX.512.66.0F38.W1 9C /r | AVX10.1 or AVX512F |
VFNMADD132PD zmm {k}{z}, zmm, m512/m64bcst
VFNMADD132PD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512 | EVEX.512.66.0F38.W1 9C /r | AVX10.1 or AVX512F |
VFNMADD132PD xmm {k}{z}, xmm, xmm
VFNMADD132PD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512 | EVEX.128.66.0F38.W1 9C /r | AVX10.1 or AVX512F + AVX512VL |
VFNMADD132PD xmm {k}{z}, xmm, m128/m64bcst
VFNMADD132PD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512 | EVEX.128.66.0F38.W1 9C /r | AVX10.1 or AVX512F + AVX512VL |
VFNMADD132PD ymm {k}{z}, ymm, ymm
VFNMADD132PD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512 | EVEX.256.66.0F38.W1 9C /r | AVX10.1 or AVX512F + AVX512VL |
VFNMADD132PD ymm {k}{z}, ymm, m256/m64bcst
VFNMADD132PD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512 | EVEX.256.66.0F38.W1 9C /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m64bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m64bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm, {er} | zmm {k}{z}, zmm, m512/m64bcst |
|---|---|---|---|---|---|---|
| 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 double works alike: 2, 4 and 8 doubles 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 m64bcst, one double from memory stands for every element of the last source. The sources are drawn above the result, each element in its own column.
Result double i comes from double i of xmm1, xmm2 and xmm3. Result doubles 1 to 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 // 64):
if k1[i]: # 1 without a write mask
a = zmm1.f64[i]
b = zmm2.f64[i]
c = src3.f64[i]
zmm1.f64[i] = fnmadd(a, c, b)
elif zeroing:
zmm1.f64[i] = 0
# else: zmm1.f64[i] keeps its value
# m64bcst: src3.f64[i] is the m64 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 |
|---|---|---|
VFNMADD132PD xmm, xmm, xmm/m128 VFNMADD132PD ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | read, write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VFNMADD132PD xmm {k}{z}, xmm, xmm/m128/m64bcst VFNMADD132PD ymm {k}{z}, ymm, ymm/m256/m64bcst VFNMADD132PD zmm {k}{z}, zmm, zmm/m512/m64bcst, {er} | ||
xmm, ymm, zmm | explicit | read, write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | 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 VFNMADD132PD, 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_pd
__m128d _mm_fnmadd_pd(__m128d __A, __m128d __B, __m128d __C) |
|
_mm_mask_fnmadd_pd
__m128d _mm_mask_fnmadd_pd(__m128d __A, __mmask8 __U, __m128d __B, __m128d __C) |
|
_mm_maskz_fnmadd_pd
__m128d _mm_maskz_fnmadd_pd(__mmask8 __U, __m128d __A, __m128d __B, __m128d __C) |
|
_mm256_fnmadd_pd
__m256d _mm256_fnmadd_pd(__m256d __A, __m256d __B, __m256d __C) |
|
_mm256_mask_fnmadd_pd
__m256d _mm256_mask_fnmadd_pd(__m256d __A, __mmask8 __U, __m256d __B, __m256d __C) |
|
_mm256_maskz_fnmadd_pd
__m256d _mm256_maskz_fnmadd_pd(__mmask8 __U, __m256d __A, __m256d __B, __m256d __C) |
|
_mm512_fnmadd_pd
__m512d _mm512_fnmadd_pd(__m512d __A, __m512d __B, __m512d __C) |
|
_mm512_mask_fnmadd_pd
__m512d _mm512_mask_fnmadd_pd(__m512d __A, __mmask8 __U, __m512d __B, __m512d __C) |
|
_mm512_mask_fnmadd_round_pd
__m512d _mm512_mask_fnmadd_round_pd(__m512d A, __mmask8 U, __m512d B, __m512d C, const int R) |
|
_mm512_maskz_fnmadd_pd
__m512d _mm512_maskz_fnmadd_pd(__mmask8 __U, __m512d __A, __m512d __B, __m512d __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
- VFMADDSUB231PD
- VFMADDSUB231PS
- VFMSUB132PD
- VFMSUB132PS
- VFMSUB132SD
- VFMSUB132SS
- VFMSUB213PD
- VFMSUB213PS
- VFMSUB213SD
- VFMSUB213SS
- VFMSUB231PD
- VFMSUB231PS
- VFMSUB231SD
- VFMSUB231SS
- VFMSUBADD132PD
- VFMSUBADD132PS
- VFMSUBADD213PD
- VFMSUBADD213PS
- VFMSUBADD231PD
- VFMSUBADD231PS
- VFNMADD132PS
- VFNMADD132SD
- VFNMADD132SS
- VFNMADD213PD
- VFNMADD213PS
- VFNMADD213SD
- VFNMADD213SS
- VFNMADD231PD
- VFNMADD231PS
- VFNMADD231SD
- VFNMADD231SS
- VFNMSUB132PD
- VFNMSUB132PS
- VFNMSUB132SD
- VFNMSUB132SS
- VFNMSUB213PD
- VFNMSUB213PS
- VFNMSUB213SD
- VFNMSUB213SS
- VFNMSUB231PD
More AVX10.1 instructions
- VFMSUB213SD
- VFMSUB213SH
- VFMSUB213SS
- VFMSUB231PD
- VFMSUB231PH
- VFMSUB231PS
- VFMSUB231SD
- VFMSUB231SH
- VFMSUB231SS
- VFMSUBADD132PD
- VFMSUBADD132PH
- VFMSUBADD132PS
- VFMSUBADD213PD
- VFMSUBADD213PH
- VFMSUBADD213PS
- VFMSUBADD231PD
- VFMSUBADD231PH
- VFMSUBADD231PS
- VFMULCPH
- VFMULCSH
- VFNMADD132PH
- VFNMADD132PS
- VFNMADD132SD
- VFNMADD132SH
- VFNMADD132SS
- VFNMADD213PD
- VFNMADD213PH
- VFNMADD213PS
- VFNMADD213SD
- VFNMADD213SH
- VFNMADD213SS
- VFNMADD231PD
- VFNMADD231PH
- VFNMADD231PS
- VFNMADD231SD
- VFNMADD231SH
- VFNMADD231SS
- VFNMSUB132PD
- VFNMSUB132PH
- VFNMSUB132PS
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-305 (VFNMADD132PD/
VFNMADD213PD/ VFNMADD231PD) - 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.