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

VFNMADD213PD computes -(op2 × op1) + op3 for each double, rounded once: the destination is a factor and the addend is the operand that may come from memory, which suits c - x × y with c in memory. It is the double form of VFNMADD213PS; VFNMADD231PS covers the negated family. 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, an addend 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, Clang 23 uses VFNMADD213PD on ymm registers, with -march=x86-64-v3 and -v4, for w[i] = z[i] - x[i] * y[i] and w[i] -= x[i] * y[i], the addend from memory, where GCC 14 takes VFNMADD132PD. For w[i] = z[i] - x[i] * k, k in a register, both compilers use VFNMADD213PD with z[i] from memory. In the polynomial 2 - (1 - (0.5 - 0.25 * t) * t) * t, Clang loads t = x[i] once: a VFMADD213PD with the constant -0.25, then two VFNMADD213PD.

Recorded on Zen 5

  • -(3 × 0.1) + (-0.3) ran in two rounding directions: vfnmadd213pd xmm1, xmm2, xmmword ptr [mem] under MXCSR 7F80H (toward zero) gave BFE3333333333333H, and vfnmadd213pd ymm0{k2}{z}, ymm31, ymm16 under BF80H (round down) BFE3333333333334H, one double further from zero.
  • Under 3FC0H (round down, DAZ), vfnmadd213pd xmm1, xmm2, xmm3 computed -(2^-1022 × 0.5) + 2^-1074 as 8008000000000000H, exactly -2^-1023: DAZ counted the denormal addend as zero, while the denormal result stayed, FTZ being clear.
  • Under DF80H (round up, FTZ), vfnmadd213pd ymm1, ymm2, ymm3 gave the most negative finite double for -(largest × 2) + (-largest), where rounding up stops a negative overflow.

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

Every encoding of VFNMADD213PD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VFNMADD213PD xmm, xmm, m128 VFNMADD213PD_XMMdq_XMMdq_MEMdqVEX.128.66.0F38.W1 AC /rFMA + AVX
VFNMADD213PD xmm, xmm, xmm VFNMADD213PD_XMMdq_XMMdq_XMMdqVEX.128.66.0F38.W1 AC /rFMA + AVX
VFNMADD213PD ymm, ymm, m256 VFNMADD213PD_YMMqq_YMMqq_MEMqqVEX.256.66.0F38.W1 AC /rFMA + AVX
VFNMADD213PD ymm, ymm, ymm VFNMADD213PD_YMMqq_YMMqq_YMMqqVEX.256.66.0F38.W1 AC /rFMA + AVX
VFNMADD213PD zmm {k}{z}, zmm, zmm, {er} VFNMADD213PD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F38.W1 AC /rAVX10.1 or AVX512F
VFNMADD213PD zmm {k}{z}, zmm, m512/m64bcst VFNMADD213PD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F38.W1 AC /rAVX10.1 or AVX512F
VFNMADD213PD xmm {k}{z}, xmm, xmm VFNMADD213PD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F38.W1 AC /rAVX10.1 or AVX512F + AVX512VL
VFNMADD213PD xmm {k}{z}, xmm, m128/m64bcst VFNMADD213PD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F38.W1 AC /rAVX10.1 or AVX512F + AVX512VL
VFNMADD213PD ymm {k}{z}, ymm, ymm VFNMADD213PD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F38.W1 AC /rAVX10.1 or AVX512F + AVX512VL
VFNMADD213PD ymm {k}{z}, ymm, m256/m64bcst VFNMADD213PD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F38.W1 AC /rAVX10.1 or AVX512F + AVX512VL

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, m128
xmm {k}{z}, xmm, m128/m64bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m64bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmm, {er}zmm {k}{z}, zmm, m512/m64bcst
Haswell11 / 0.5p015 / 0.5p0112 / 0.5p015 / 0.5p01
Broadwell10 / 0.5p015 / 0.5p0111 / 0.5p015 / 0.5p01
Skylake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p01
Skylake-SP10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 0.5p0511 / 0.5p05
Ice Lake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 1p011 / 1p0
Alder Lake11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p014 / 1p012 / 1p0
Lunar Lake10 / 2V0 V14 / 2V0 V111 / 2.33V0 V14 / 2V0 V1
Piledriver10 / 1.5FPFMA FPU0 FPU15 / 1.5FPFMA FPU0 FPU1 FPU2 FPU310 / 1.5FPFMA FPU0 FPU15 / 1.5FPFMA FPU0 FPU1 FPU2 FPU3
Zen12 / 0.5FPU0 FPU15 / 0.5FPU0 FPU112 / 1FPU0 FPU15 / 1FPU0 FPU1
Zen 212 / 0.5FPU0 FPU15 / 0.5FPU0 FPU112 / 0.5FPU0 FPU15 / 0.5FPU0 FPU1
Zen 311 / 0.5FP0 FP14 / 0.5FP0 FP111 / 0.5FP0 FP14 / 0.5FP0 FP1
Zen 411 / 0.5FP0 FP14 / 0.5FP0 FP111 / 0.5FP0 FP14 / 0.5FP0 FP14 / 1FP0 FP111 / 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.

Element-wise: each double of the result comes from the double in the same place in each source.
VFNMADD213PD: element by elementResult double i comes from double i of xmm1, xmm2 and xmm3. Result doubles 1 to 0: r1, r0.01xmm1a01xmm2b01xmm3or m128c11k1r0r1xmm1

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(b, a, c)
    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 up

Run on AMD Zen 5 (EPYC 9645): 15 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
VFNMADD213PD xmm, xmm, xmm/m128 VFNMADD213PD ymm, ymm, ymm/m256
xmm, ymmexplicitread, write
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VFNMADD213PD xmm {k}{z}, xmm, xmm/m128/m64bcst VFNMADD213PD ymm {k}{z}, ymm, ymm/m256/m64bcst VFNMADD213PD zmm {k}{z}, zmm, zmm/m512/m64bcst, {er}
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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 VFNMADD213PD, 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_fnmadd_pd __m128d _mm_fnmadd_pd(__m128d __A, __m128d __B, __m128d __C)

VFNMADD213PD xmm, xmm, xmm VEX.128 -mfma

_mm_mask_fnmadd_pd __m128d _mm_mask_fnmadd_pd(__m128d __A, __mmask8 __U, __m128d __B, __m128d __C)

VFNMADD213PD xmm {k}, xmm, m128/m64bcst EVEX.128 -mavx512vlwhen __C comes from memory

_mm_maskz_fnmadd_pd __m128d _mm_maskz_fnmadd_pd(__mmask8 __U, __m128d __A, __m128d __B, __m128d __C)

VFNMADD213PD xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl

_mm256_fnmadd_pd __m256d _mm256_fnmadd_pd(__m256d __A, __m256d __B, __m256d __C)

VFNMADD213PD ymm, ymm, ymm VEX.256 -mfma

_mm256_mask_fnmadd_pd __m256d _mm256_mask_fnmadd_pd(__m256d __A, __mmask8 __U, __m256d __B, __m256d __C)

VFNMADD213PD ymm {k}, ymm, m256/m64bcst EVEX.256 -mavx512vlwhen __C comes from memory

_mm256_maskz_fnmadd_pd __m256d _mm256_maskz_fnmadd_pd(__mmask8 __U, __m256d __A, __m256d __B, __m256d __C)

VFNMADD213PD ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm512_fnmadd_pd __m512d _mm512_fnmadd_pd(__m512d __A, __m512d __B, __m512d __C)

VFNMADD213PD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_fnmadd_round_pd __m512d _mm512_fnmadd_round_pd(__m512d A, __m512d B, __m512d C, const int R)

VFNMADD213PD zmm, zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_mask_fnmadd_pd __m512d _mm512_mask_fnmadd_pd(__m512d __A, __mmask8 __U, __m512d __B, __m512d __C)

VFNMADD213PD zmm {k}, zmm, m512/m64bcst EVEX.512 -mavx512fwhen __C comes from memory

_mm512_maskz_fnmadd_pd __m512d _mm512_maskz_fnmadd_pd(__mmask8 __U, __m512d __A, __m512d __B, __m512d __C)

VFNMADD213PD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_fnmadd_round_pd __m512d _mm512_maskz_fnmadd_round_pd(__mmask8 U, __m512d A, __m512d B, __m512d C, const int R)

VFNMADD213PD zmm {k}{z}, zmm, zmm, {er} EVEX.512 -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.
ISA setCPUIDProcessors
FMA

FMA + AVX
CPUID.01H:ECX[12] FMA
CPUID.01H:ECX[28] AVX

XED and Intel’s SDM differ: XED also asks for the AVX bit, CPUID.01H:ECX[28], besides FMA, CPUID.01H:ECX[12]. The opcode tables of revision 093 of Intel’s SDM name FMA alone for every VEX form, but its Volume 1 tells software to check for AVX first and then for FMA, so in effect the two agree.

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
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] 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
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
CPUID.(EAX=07H,ECX=0):EBX[31] 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_128Same as AVX512F_128

More FMA instructions

All 60 FMA 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 2C, page 5-305 (VFNMADD132PD/VFNMADD213PD/VFNMADD231PD)
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  7. Software Optimization Guide for the AMD Zen5 Microarchitecture (58455, rev. 1.00, August 2024), Wayback Machine copy of AMD's ZIP
  8. 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.