x86-64.net

Instruction

VFMADD132SD

Fused multiply-add of the low doubles: first times third plus second, into the first; the rest is unchanged.

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

VFMADD132SD computes op1 × op3 + op2 for the low double and rounds once: the destination and the operand that may come from memory are the factors, the middle register the addend. The high double keeps the destination’s value and bits 511:128 are cleared. VFMADD132PD is the packed form, VFMADD132PS shows the operand roles of the 132 form, and VFMADD231SS what the scalar forms change. VFMADD132SS is the single form.

In our builds

At -O2 with -march=x86-64-v3 or -v4, GCC 14 compiles fma(a, b, c) on three double arguments to vfmadd132sd xmm0, xmm2, xmm1, and da = da * db + dc over globals with db from memory; Clang 23 uses VFMADD213SD for both. In a loop s = fma(x[i], y[i], s) Clang alternates the sum between two registers with VFMADD132SD, x[i] loaded into the register that does not hold the sum.

Recorded on Zen 5

  • In vfmadd132sd xmm17{k7}{z}, xmm30, qword ptr [mem], under FFC0H, the destination held the quiet NaN 7FF8000000012345H, XMM30 the quiet NaN FFF8000000000005H and memory a signaling NaN. The result was 7FF8000000012345H, a factor’s NaN rather than the addend’s, as Intel’s table of FMA results (Volume 1, Table 14-17) ranks them, and IE was set for the signaling NaN.
  • Under 3FC0H (round down), vfmadd132sd xmm12, xmm6, xmm6 computed the largest double × 2 + 2 as the largest double, not infinity, and set OE 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

Every encoding of VFMADD132SD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VFMADD132SD xmm, xmm, m64 VFMADD132SD_XMMdq_XMMq_MEMqVEX.LIG.66.0F38.W1 99 /rFMA + AVX
VFMADD132SD xmm, xmm, xmm VFMADD132SD_XMMdq_XMMq_XMMqVEX.LIG.66.0F38.W1 99 /rFMA + AVX
VFMADD132SD xmm {k}{z}, xmm, xmm, {er} VFMADD132SD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.LIG.66.0F38.W1 99 /rAVX10.1 or AVX512F
VFMADD132SD xmm {k}{z}, xmm, m64 VFMADD132SD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.LIG.66.0F38.W1 99 /rAVX10.1 or AVX512F

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, m64
xmm {k}{z}, xmm, m64		xmm, xmm, xmm
xmm {k}{z}, xmm, xmm, {er}
Haswell, Broadwell10 / 0.5p015 / 0.5p01
Skylake, Skylake-SP, Ice Lake9 / 0.5p014 / 0.5p01
Alder Lake, Sapphire Rapids11 / 0.5p014 / 0.5p01
Lunar Lake10 / 2V0 V14 / 2V0 V1
Piledriver10 / 1.5FPFMA FPU0 FPU15 / 1.5FPFMA FPU0 FPU1 FPU2 FPU3
Zen, Zen 212 / 0.5FPU0 FPU15 / 0.5FPU0 FPU1
Zen 311 / 0.5FP0 FP14 / 0.5FP0 FP1
Zen 411 / 1FP0 FP14 / 11FP0 FP1
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 1171; AMD 58455, row 1342).

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.

Scalar: only the low double is computed; the other double comes from xmm1.
VFMADD132SD: the low elementResult double 0 is computed from double 0 of xmm1, xmm2 and xmm3; double 1 is that of xmm1. Result doubles 1 to 0: a1, r0.01xmm1a1k1r0a1xmm101xmm2b01xmm3or m64c

The write mask k1 applies to the low double: with bit 0 clear it keeps its old value, or is zeroed with {z}.

Result double 0 is computed from double 0 of xmm1, xmm2 and xmm3; double 1 is that of xmm1. Result doubles 1 to 0: 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.f64[0]
    b = xmm2.f64[0]
    c = src3.f64[0]
    xmm1.f64[0] = fmadd(a, c, b)
elif zeroing:
    xmm1.f64[0] = 0
# else: xmm1.f64[0] keeps its value
# xmm1.q[1] keeps its value
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 6 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
VFMADD132SD xmm, xmm, xmm/m64
xmmexplicitread, write
xmmexplicitread
xmm/m64explicitread
VFMADD132SD xmm {k}{z}, xmm, xmm/m64, {er}
xmmexplicitread, write (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m64explicitread

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 VFMADD132SD, 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_fmadd_sd __m128d _mm_fmadd_sd(__m128d __A, __m128d __B, __m128d __C)

VFMADD132SD xmm, xmm, m64 VEX.LIG -mfmawhen __B comes from memory

_mm_mask_fmadd_sd __m128d _mm_mask_fmadd_sd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B)

VFMADD132SD xmm {k}, xmm, m64 EVEX.LIG -mavx512fwhen __A comes from memory

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

VFMADD132SD xmm {k}{z}, xmm, m64 EVEX.LIG -mavx512fwhen __B comes from memory

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_SCALAR

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

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-226 (VFMADD132SD/VFMADD213SD/VFMADD231SD)
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  7. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  8. 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.