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

VFMULCSH multiplies the lowest complex number of its first source, the halves in bits 15:0 (real) and 31:16 (imaginary), by that of the second: for a + bi times c + di it writes ac - bd and ad + bc to the low 32 bits of the destination. Bits 127:32 come from the first source and the bits above 127 are cleared. It is the scalar form of VFMULCPH, whose page covers the pair layout, the rounding after each internal step and the exceptions, which set MXCSR’s flags but never fault; VFCMULCSH conjugates the second factor, and VADDPH covers the format and the CPUID bits.

A scalar of 32 bits

The scalar here is a pair, so the write mask uses bit 0 for both halves and a memory operand is 32 bits, where the real scalar FP16 instructions such as VMULSH read 16. The encoding is D7h with the F3 prefix in EVEX map 6, one above the packed form’s D6h; it takes {er} between registers. As for the packed form, the destination register must differ from both sources, or the instruction raises #UD.

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, GCC 14 and Clang 23 emit VFMULCSH for the intrinsics _mm_fmul_sch and _mm_mul_sch, and _mm_fmul_round_sch with _MM_FROUND_TO_ZERO gives vfmulcsh xmm2, xmm0, xmm1, {rz-sae} followed by a move to XMM0, since the result may not overwrite the first source. A function multiplying two _Complex _Float16 values does not use it: by default both compilers compute it with scalar arithmetic and call the library’s __mulhc3 only for a NaN result, and with -ffast-math GCC computes the parts with VMULSH, VFMSUB132SH and VFMADD132SH, Clang with VMULPH and VFMADDSUB231PH on broadcast and swapped halves.

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

In the optimization guide

What the optimization guide says about VFMULCSH, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Golden Cove and Raptor Cove

Forms

Every encoding of VFMULCSH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VFMULCSH xmm {k}{z}, xmm, xmm, {er} VFMULCSH_XMM2f16_MASKmskw_XMM2f16_XMM2f16_AVX512EVEX.LIG.F3.MAP6.W0 D7 /rAVX10.1 or AVX512_FP16
VFMULCSH xmm {k}{z}, xmm, m32 VFMULCSH_XMM2f16_MASKmskw_XMM2f16_MEM2f16_AVX512EVEX.LIG.F3.MAP6.W0 D7 /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, m32no maskxmm {k}{z}, xmm, m32with a mask, zeroing
Sapphire Rapids9 / 1p0115 / 1p0116 / 1p0121 / 1p01

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 FP16 pair is computed; the other FP16 pairs come from xmm2.
VFMULCSH: the low elementResult FP16 pair 0 is computed from FP16 pair 0 of xmm2 and xmm3; FP16 pairs 3 to 1 are those of xmm2. Result FP16 pairs 3 to 0: a3, a2, a1, r0.0123xmm2a1k1r0a1a2a3xmm10123xmm3or m32b

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

Result FP16 pair 0 is computed from FP16 pair 0 of xmm2 and xmm3; FP16 pairs 3 to 1 are those of xmm2. Result FP16 pairs 3 to 0: 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 xmm1.number == xmm2.number:
    fault(UD)
if not src3.is_memory:
    if xmm1.number == src3.number:
        fault(UD)
if k1[0]:
    ar = xmm2.f16[0]
    ai = xmm2.f16[1]
    br = src3.f16[0]
    bi = src3.f16[1]
    x = mul(ar, br)
    y = mul(ai, br)
    x = fnmadd(ai, bi, x)
    y = fmadd(ar, bi, y)
    xmm1.d[0] = y << 16 | x
elif zeroing:
    xmm1.d[0] = 0
# else: xmm1.d[0] keeps its value
for i in range(1, 4):
    xmm1.d[i] = xmm2.d[i]
# (ar + ai*i)(br + bi*i) = x + y*i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# exceptions as if masked (flags, never #XM): the SDM's claim, unchecked here
# 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
VFMULCSH xmm {k}{z}, xmm, xmm/m32, {er}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m32explicitread

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

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 VFMULCSH, 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_fmul_round_sch __m128h _mm_fmul_round_sch(__m128h A, __m128h B, const int R)

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

_mm_fmul_sch __m128h _mm_fmul_sch(__m128h __A, __m128h __B)

VFMULCSH xmm, xmm, xmm EVEX.LIG -mavx512fp16

_mm_mul_round_sch __m128h _mm_mul_round_sch(__m128h A, __m128h B, const int R)

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

_mm_mul_sch __m128h _mm_mul_sch(__m128h A, __m128h B)

VFMULCSH xmm, xmm, xmm EVEX.LIG -mavx512fp16

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

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

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

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

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

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

_mm_mask_mul_sch __m128h _mm_mask_mul_sch(__m128h W, __mmask8 U, __m128h A, __m128h B)

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

_mm_maskz_fmul_round_sch __m128h _mm_maskz_fmul_round_sch(__mmask8 U, __m128h A, __m128h B, const int R)

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

_mm_maskz_fmul_sch __m128h _mm_maskz_fmul_sch(__mmask8 __U, __m128h __A, __m128h __B)

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

_mm_maskz_mul_round_sch __m128h _mm_maskz_mul_round_sch(__mmask8 U, __m128h A, __m128h B, const int R)

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

_mm_maskz_mul_sch __m128h _mm_maskz_mul_sch(__mmask8 U, __m128h A, __m128h B)

VFMULCSH 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-189 (VFCMULCSH/VFMULCSH)
  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.