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

VFMSUB213SH computes op2 × op1 - op3 on the low halves and rounds once: op1 is a factor and is overwritten, and op3, the operand that may come from memory, is subtracted. Bits 127:16 of the destination stay as they were and the bits above 127 are cleared. It is the scalar form of VFMSUB213PH; VFMSUB132SH and VFMSUB231SH are the other operand orders, VFMADD213SH the 213 order with an addend, and VFMSUB213SS the single-precision form. The encoding is ABh with the 66 prefix in EVEX map 6; it takes {er} between registers and reads two bytes from memory.

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, Clang 23 compiles x * y - z, __builtin_fmaf16(x, y, -z) and _mm_fmsub_sh(a, b, c) on _Float16 values to VFMSUB213SH, and the masked _mm_mask_fmsub_sh and _mm_maskz_fmsub_sh too, since either of the first two orders keeps the first factor in the destination; GCC 14 picks VFMSUB132SH for all of these. Both use VFMSUB213SH when the subtracted value comes from memory, as in x * y - a[5].

A constant is the exception: x * y - 1 does not subtract at all, but becomes VFMADD213SH adding -1 read from memory, in both compilers. In a loop r[i] = p[i] * q[i] - r[i] through pointer parameters, Clang loads the two factors and reads r[i] in place with VFMSUB213SH for short or overlapping arrays, and otherwise runs VFMSUB213PH on ymm registers after a run-time check that the arrays do not overlap; GCC keeps the loop scalar with VFMSUB132SH.

Intel’s optimization manual counts the fused multiply-add among the FP16 operations that are correctly rounded, to 0.5 ULP when rounding to nearest (Section 18.5.3).

AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VFMSUB213SH.

Forms

Every encoding of VFMSUB213SH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VFMSUB213SH xmm {k}{z}, xmm, xmm, {er} VFMSUB213SH_XMMf16_MASKmskw_XMMf16_XMMf16_AVX512EVEX.LIG.66.MAP6.W0 AB /rAVX10.1 or AVX512_FP16
VFMSUB213SH xmm {k}{z}, xmm, m16 VFMSUB213SH_XMMf16_MASKmskw_XMMf16_MEMf16_AVX512EVEX.LIG.66.MAP6.W0 AB /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, xmm, {er}no mask, with {er}xmm {k}{z}, xmm, xmm, {er}with a mask, zeroingxmm {k}{z}, xmm, m16
Sapphire Rapids5 / 0.5p016 / 0.5p0112 / 0.5p01

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 half is computed; the other halves come from xmm1.
VFMSUB213SH: the low elementResult half 0 is computed from half 0 of xmm1, xmm2 and xmm3; halves 7 to 1 are those of xmm1. Result halves 7 to 0: a7, a6, a5, a4, a3, a2, a1, r0.01234567xmm1a1k1r0a1a2a3a4a5a6a7xmm101234567xmm2b01234567xmm3or m16c

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

Result half 0 is computed from half 0 of xmm1, xmm2 and xmm3; halves 7 to 1 are those of xmm1. Result halves 7 to 0: a7, a6, a5, a4, a3, a2, 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]:
    a = xmm1.f16[0]
    b = xmm2.f16[0]
    c = src3.f16[0]
    xmm1.f16[0] = fmsub(b, a, c)
elif zeroing:
    xmm1.f16[0] = 0
# else: xmm1.f16[0] keeps its value
# xmm1.w[1] to [7] keep their values
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 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
VFMSUB213SH xmm {k}{z}, xmm, xmm/m16, {er}
xmmexplicitread, write (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m16explicitread

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-E3

Attributes

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

All forms
write masking; follows MXCSR
Memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VFMSUB213SH, 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_fmsub_round_sh __m128h _mm_fmsub_round_sh(__m128h A, __m128h B, __m128h C, const int R)

VFMSUB213SH xmm, xmm, xmm, {er} EVEX.LIG -mavx512fp16

_mm_fmsub_sh __m128h _mm_fmsub_sh(__m128h __W, __m128h __A, __m128h __B)

VFMSUB213SH xmm, xmm, xmm EVEX.LIG -mavx512fp16

_mm_mask_fmsub_round_sh __m128h _mm_mask_fmsub_round_sh(__m128h W, __mmask8 U, __m128h A, __m128h B, const int R)

VFMSUB213SH xmm {k}, xmm, xmm, {er} EVEX.LIG -mavx512fp16

_mm_mask_fmsub_sh __m128h _mm_mask_fmsub_sh(__m128h __W, __mmask8 __U, __m128h __A, __m128h __B)

VFMSUB213SH xmm {k}, xmm, xmm EVEX.LIG -mavx512fp16

_mm_maskz_fmsub_round_sh __m128h _mm_maskz_fmsub_round_sh(__mmask8 U, __m128h A, __m128h B, __m128h C, const int R)

VFMSUB213SH xmm {k}{z}, xmm, xmm, {er} EVEX.LIG -mavx512fp16

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

VFMSUB213SH xmm {k}{z}, xmm, xmm EVEX.LIG -mavx512fp16

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_SCALAR

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

Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6

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-279 (VF[,N]MSUB[132,213,231]SH)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 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.