Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VFMADD132PH computes op1 times op3 plus op2 for each half-precision element and rounds once, writing the result over op1. It belongs to AVX512-FP16 (AVX10.1), like VADDPH, whose page covers the format, the CPUID bits and the encoding; the 132, 213 and 231 orders work as VFMADD231PS explains for singles, here on 32 elements per zmm register. The family is complete for halves: VFMSUB132PH, the negated VFNMADD132PH and VFNMSUB132PH, the alternating VFMADDSUB132PH and VFMSUBADD132PH, and the scalar VFMADD132SH.

The order decides what a mask keeps

Under merge masking an element whose mask bit is clear keeps op1. In the 132 form op1 is a factor, in the 213 form the other factor, in the 231 form the addend. So _mm512_mask_fmadd_ph(a, k, b, c), whose unselected elements must stay a, the first factor, maps to the 132 or 213 order, and _mm512_mask3_fmadd_ph(a, b, c, k), which keeps c, to 231. The only operand that may come from memory, or be broadcast from a single half, is op3, a factor in the 132 order.

In compiled code

With -march=sapphirerapids, GCC 14 compiles c[i] = a[i] * b[i] + c[i] over global _Float16 arrays to VFMADD132PH with a factor from memory, at -O2 as at -O3, and so it does for 1,024 elements through restrict pointers. Pointers without restrict keep the loop scalar at -O2, with VFMADD132SH, even for that count, and so does a count known only at run time or one such as 1,001, even over global arrays; at -O3 it vectorizes them all and finishes the remainder with VFMADD132SH. Clang 23 vectorizes them at -O2 and picks VFMADD213PH instead. Both contract the multiply and the add by default here. Without AVX512-FP16, as with -march=znver5, they widen the three operands with VCVTPH2PS, use a single-precision FMA and narrow the result with VCVTPS2PH.

Complex numbers

VFMADDCPH and VFCMADDCPH treat pairs of halves as complex numbers and do a complex multiply-add. Intel’s optimization manual explains that the hardware runs them as a sequence of FMA steps, each rounded to FP16, so their result carries more error than one rounding (Sections 18.4.3 and 18.5.3). VFMADD132PH itself is correctly rounded, and FP16 arithmetic handles denormals at full speed with MXCSR.DAZ and FTZ ignored (Section 18.5.4).

Forms

Every encoding of VFMADD132PH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VFMADD132PH xmm {k}{z}, xmm, xmm VFMADD132PH_XMMf16_MASKmskw_XMMf16_XMMf16_AVX512EVEX.128.66.MAP6.W0 98 /rAVX10.1 or AVX512_FP16 + AVX512VL
VFMADD132PH xmm {k}{z}, xmm, m128/m16bcst VFMADD132PH_XMMf16_MASKmskw_XMMf16_MEMf16_AVX512EVEX.128.66.MAP6.W0 98 /rAVX10.1 or AVX512_FP16 + AVX512VL
VFMADD132PH ymm {k}{z}, ymm, ymm VFMADD132PH_YMMf16_MASKmskw_YMMf16_YMMf16_AVX512EVEX.256.66.MAP6.W0 98 /rAVX10.1 or AVX512_FP16 + AVX512VL
VFMADD132PH ymm {k}{z}, ymm, m256/m16bcst VFMADD132PH_YMMf16_MASKmskw_YMMf16_MEMf16_AVX512EVEX.256.66.MAP6.W0 98 /rAVX10.1 or AVX512_FP16 + AVX512VL
VFMADD132PH zmm {k}{z}, zmm, zmm, {er} VFMADD132PH_ZMMf16_MASKmskw_ZMMf16_ZMMf16_AVX512EVEX.512.66.MAP6.W0 98 /rAVX10.1 or AVX512_FP16
VFMADD132PH zmm {k}{z}, zmm, m512/m16bcst VFMADD132PH_ZMMf16_MASKmskw_ZMMf16_MEMf16_AVX512EVEX.512.66.MAP6.W0 98 /rAVX10.1 or AVX512_FP16

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 {k}{z}, xmm, xmmno mask
ymm {k}{z}, ymm, ymmno mask
xmm {k}{z}, xmm, xmmwith a mask, zeroing
ymm {k}{z}, ymm, ymmwith a mask, zeroing
xmm {k}{z}, xmm, m128/m16bcst
ymm {k}{z}, ymm, m256/m16bcst
zmm {k}{z}, zmm, zmm, {er}no mask, with {er}zmm {k}{z}, zmm, zmm, {er}with a mask, zeroingzmm {k}{z}, zmm, m512/m16bcst
Sapphire Rapids5 / 0.5p016 / 0.5p0112 / 0.5p015 / 1p06 / 1p012 / 1p0

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 half of the result comes from the half in the same place in each source.
VFMADD132PH: element by elementResult half i comes from half i of xmm1, xmm2 and xmm3. Result halves 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, r1, r0.01234567xmm1a01234567xmm2b01234567xmm3or m128c11111110k1r0r1r2r3r4r5r7xmm1

Every half works alike: 8, 16 and 32 halves in the xmm, ymm and zmm forms. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m16bcst, one half from memory stands for every element of the last source. The sources are drawn above the result, each element in its own column.

Result half i comes from half i of xmm1, xmm2 and xmm3. Result halves 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, 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 // 16):
    if k1[i]:
        a = zmm1.f16[i]
        b = zmm2.f16[i]
        c = src3.f16[i]
        zmm1.f16[i] = fmadd(a, c, b)
    elif zeroing:
        zmm1.f16[i] = 0
    # else: zmm1.f16[i] keeps its value
# m16bcst: src3.f16[i] is the m16 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# zmm1 is zeroed from bit VL up

Not run on a processor: none of these processors has AVX512-FP16. The tests check its arithmetic against MPFR.

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
VFMADD132PH xmm {k}{z}, xmm, xmm/m128/m16bcst VFMADD132PH ymm {k}{z}, ymm, ymm/m256/m16bcst VFMADD132PH zmm {k}{z}, zmm, zmm/m512/m16bcst, {er}
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m16bcst, ymm/m256/m16bcst, zmm/m512/m16bcstexplicitread

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.

All forms
AVX512-E2

Attributes

What else XED records about the forms. How to read.

All forms
write masking; follows MXCSR
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VFMADD132PH, 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_ph __m128h _mm_fmadd_ph(__m128h __A, __m128h __B, __m128h __C)

VFMADD132PH xmm, xmm, m128/m16bcst EVEX.128 -mavx512fp16 -mavx512vlwhen __A comes from memory

_mm_mask_fmadd_ph __m128h _mm_mask_fmadd_ph(__m128h __A, __mmask8 __U, __m128h __B, __m128h __C)

VFMADD132PH xmm {k}, xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_maskz_fmadd_ph __m128h _mm_maskz_fmadd_ph(__mmask8 __U, __m128h __A, __m128h __B, __m128h __C)

VFMADD132PH xmm {k}{z}, xmm, m128/m16bcst EVEX.128 -mavx512fp16 -mavx512vlwhen __A comes from memory

_mm256_fmadd_ph __m256h _mm256_fmadd_ph(__m256h __A, __m256h __B, __m256h __C)

VFMADD132PH ymm, ymm, m256/m16bcst EVEX.256 -mavx512fp16 -mavx512vlwhen __A comes from memory

_mm256_mask_fmadd_ph __m256h _mm256_mask_fmadd_ph(__m256h __A, __mmask16 __U, __m256h __B, __m256h __C)

VFMADD132PH ymm {k}, ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_maskz_fmadd_ph __m256h _mm256_maskz_fmadd_ph(__mmask16 __U, __m256h __A, __m256h __B, __m256h __C)

VFMADD132PH ymm {k}{z}, ymm, m256/m16bcst EVEX.256 -mavx512fp16 -mavx512vlwhen __A comes from memory

_mm512_fmadd_ph __m512h _mm512_fmadd_ph(__m512h __A, __m512h __B, __m512h __C)

VFMADD132PH zmm, zmm, m512/m16bcst EVEX.512 -mavx512fp16when __A comes from memory

_mm512_mask_fmadd_ph __m512h _mm512_mask_fmadd_ph(__m512h __A, __mmask32 __U, __m512h __B, __m512h __C)

VFMADD132PH zmm {k}, zmm, zmm EVEX.512 -mavx512fp16

_mm512_mask_fmadd_round_ph __m512h _mm512_mask_fmadd_round_ph(__m512h A, __mmask32 U, __m512h B, __m512h C, const int R)

VFMADD132PH zmm {k}, zmm, zmm, {er} EVEX.512 -mavx512fp16

_mm512_maskz_fmadd_ph __m512h _mm512_maskz_fmadd_ph(__mmask32 __U, __m512h __A, __m512h __B, __m512h __C)

VFMADD132PH zmm {k}{z}, zmm, m512/m16bcst EVEX.512 -mavx512fp16when __A 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
AVX512_FP16_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512_FP16 + AVX512VL
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6
AVX512_FP16_256
Same as AVX512_FP16_128Same as AVX512_FP16_128
AVX512_FP16_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512_FP16
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16

Same as AVX512_FP16_128

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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-214 (VF[,N]MADD[132,213,231]PH)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 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.