Instruction
VFNMSUB213PH
Fused negated multiply-subtract of packed half-precision values: minus second operand times first, minus third, into the first.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VFNMSUB213PH computes -(op2 × op1) - op3 for each half-precision element
and rounds once, writing over op1: the destination is a factor, and the
operand that may come from memory, or be broadcast from one half, is
subtracted from the negated product. VFNMSUB132PH
covers the negated subtracting FP16 forms,
VFNMSUB231PS how they differ from a negated
VFMADD, and VFNMSUB213PS is the single-precision
form. The opcode is AEh with the 66 prefix in EVEX map 6; rounding
follows MXCSR.RC, or {er} on the 512-bit register form, and denormals
are kept whatever DAZ and FTZ say, as VADDPH explains.
Clang’s order
At -O2 with -march=x86-64-v4 -mavx512fp16, Clang 23 compiles c[i] = -(a[i] * b[i]) - d[i] over _Float16 arrays to VFNMSUB213PH on ymm
registers, both factors loaded and d[i] read from memory, and
_mm512_fnmsub_ph(a, b, c) on three registers too; GCC 14 uses
VFNMSUB132PH for both, with a factor from memory in the loop.
A constant shows the compilers apart again. _mm512_fnmsub_ph(x, y, _mm512_set1_ph(1.0f16)) stays VFNMSUB213PH in GCC, with the half 1.0
broadcast from memory by {1to32}; Clang negates the constant and emits
VFNMADD213PH with -1 broadcast instead, the same
value -(x × y) - 1 rounded once.
Not a VFMADD with a sign flip
-(x × y) - z and -(x × y + z) differ when x × y + z is exactly zero: the
first gives +0 under round to nearest, the second -0, and under rounding
up or down the two round in opposite directions. Neither compiler turns
-_mm512_fmadd_ph(a, b, c) into this instruction: both keep VFMADD and
flip the sign bits with an XOR.
AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VFNMSUB213PH.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VFNMSUB213PH xmm {k}{z}, xmm, xmm
VFNMSUB213PH_XMMf16_MASKmskw_XMMf16_XMMf16_AVX512 | EVEX.128.66.MAP6.W0 AE /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFNMSUB213PH xmm {k}{z}, xmm, m128/m16bcst
VFNMSUB213PH_XMMf16_MASKmskw_XMMf16_MEMf16_AVX512 | EVEX.128.66.MAP6.W0 AE /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFNMSUB213PH ymm {k}{z}, ymm, ymm
VFNMSUB213PH_YMMf16_MASKmskw_YMMf16_YMMf16_AVX512 | EVEX.256.66.MAP6.W0 AE /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFNMSUB213PH ymm {k}{z}, ymm, m256/m16bcst
VFNMSUB213PH_YMMf16_MASKmskw_YMMf16_MEMf16_AVX512 | EVEX.256.66.MAP6.W0 AE /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFNMSUB213PH zmm {k}{z}, zmm, zmm, {er}
VFNMSUB213PH_ZMMf16_MASKmskw_ZMMf16_ZMMf16_AVX512 | EVEX.512.66.MAP6.W0 AE /r | AVX10.1 or AVX512_FP16 |
VFNMSUB213PH zmm {k}{z}, zmm, m512/m16bcst
VFNMSUB213PH_ZMMf16_MASKmskw_ZMMf16_MEMf16_AVX512 | EVEX.512.66.MAP6.W0 AE /r | AVX10.1 or AVX512_FP16 |
Latency and throughput
| Model | xmm {k}{z}, xmm, xmmno maskymm {k}{z}, ymm, ymmno mask | xmm {k}{z}, xmm, xmmwith a mask, zeroingymm {k}{z}, ymm, ymmwith a mask, zeroing | xmm {k}{z}, xmm, m128/m16bcstymm {k}{z}, ymm, m256/m16bcst | zmm {k}{z}, zmm, zmm, {er}no mask, with {er} | zmm {k}{z}, zmm, zmm, {er}with a mask, zeroing | zmm {k}{z}, zmm, m512/m16bcst |
|---|---|---|---|---|---|---|
| Sapphire Rapids | 5 / 0.5p01 | 6 / 0.5p01 | 12 / 0.5p01 | 5 / 1p0 | 6 / 1p0 | 12 / 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.
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] = fnmsub(b, a, c)
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 upNot run on a processor: none of these processors has AVX512-FP16. The tests check its arithmetic against MPFR.
Operands
| Operand | Kind | Action |
|---|---|---|
VFNMSUB213PH xmm {k}{z}, xmm, xmm/m128/m16bcst VFNMSUB213PH ymm {k}{z}, ymm, ymm/m256/m16bcst VFNMSUB213PH zmm {k}{z}, zmm, zmm/m512/m16bcst, {er} | ||
xmm, ymm, zmm | explicit | read, write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m16bcst, ymm/m256/m16bcst, zmm/m512/m16bcst | 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.
- 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 VFNMSUB213PH, 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_ph
__m128h _mm_fnmsub_ph(__m128h __A, __m128h __B, __m128h __C) |
|
_mm_mask_fnmsub_ph
__m128h _mm_mask_fnmsub_ph(__m128h __A, __mmask8 __U, __m128h __B, __m128h __C) |
|
_mm_maskz_fnmsub_ph
__m128h _mm_maskz_fnmsub_ph(__mmask8 __U, __m128h __A, __m128h __B, __m128h __C) |
|
_mm256_fnmsub_ph
__m256h _mm256_fnmsub_ph(__m256h __A, __m256h __B, __m256h __C) |
|
_mm256_mask_fnmsub_ph
__m256h _mm256_mask_fnmsub_ph(__m256h __A, __mmask16 __U, __m256h __B, __m256h __C) |
|
_mm256_maskz_fnmsub_ph
__m256h _mm256_maskz_fnmsub_ph(__mmask16 __U, __m256h __A, __m256h __B, __m256h __C) |
|
_mm512_fnmsub_ph
__m512h _mm512_fnmsub_ph(__m512h __A, __m512h __B, __m512h __C) |
|
_mm512_fnmsub_round_ph
__m512h _mm512_fnmsub_round_ph(__m512h A, __m512h B, __m512h C, const int R) |
|
_mm512_mask_fnmsub_ph
__m512h _mm512_mask_fnmsub_ph(__m512h __A, __mmask32 __U, __m512h __B, __m512h __C) |
|
_mm512_maskz_fnmsub_ph
__m512h _mm512_maskz_fnmsub_ph(__mmask32 __U, __m512h __A, __m512h __B, __m512h __C) |
|
_mm512_maskz_fnmsub_round_ph
__m512h _mm512_maskz_fnmsub_round_ph(__mmask32 U, __m512h A, __m512h B, __m512h C, const int R) |
|
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 |
|---|---|---|
AVX512_FP16_128 | AVX10.1 or AVX512_FP16 + AVX512VL | Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6 |
AVX512_FP16_256 | Same as AVX512_FP16_128 | Same as AVX512_FP16_128 |
AVX512_FP16_512 | AVX10.1 or AVX512_FP16 | Same as AVX512_FP16_128 |
More AVX10.1 instructions
- VFNMADD132SS
- VFNMADD213PD
- VFNMADD213PH
- VFNMADD213PS
- VFNMADD213SD
- VFNMADD213SH
- VFNMADD213SS
- VFNMADD231PD
- VFNMADD231PH
- VFNMADD231PS
- VFNMADD231SD
- VFNMADD231SH
- VFNMADD231SS
- VFNMSUB132PD
- VFNMSUB132PH
- VFNMSUB132PS
- VFNMSUB132SD
- VFNMSUB132SH
- VFNMSUB132SS
- VFNMSUB213PD
- VFNMSUB213PS
- VFNMSUB213SD
- VFNMSUB213SH
- VFNMSUB213SS
- VFNMSUB231PD
- VFNMSUB231PH
- VFNMSUB231PS
- VFNMSUB231SD
- VFNMSUB231SH
- VFNMSUB231SS
- VFPCLASSPD
- VFPCLASSPH
- VFPCLASSPS
- VFPCLASSSD
- VFPCLASSSH
- VFPCLASSSS
- VGATHERDPD
- VGATHERDPS
- VGATHERQPD
- VGATHERQPS
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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-263 (VF[,N]MSUB[132,213,231]PH)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
- 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.