Instruction
VFCMADDCPH
Multiplies packed complex half-precision numbers by the complex conjugates of the second source and adds the products to the destination.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VFCMADDCPH multiplies each complex number of its first source by the
complex conjugate of the matching one in the second and adds the product
to the destination: acc += x × conj(y) for 16 complex values, pairs of
halves, per zmm register. For x = a + bi and y = c + di the real part
gains ac + bd and the imaginary part bc - ad. It is
VFMADDCPH with the conjugate, F2 instead of F3 on
opcode 56h in EVEX map 6, and that page covers the accumulator in the
destination and the masked intrinsics; VFCMULCPH
explains which operand is conjugated, VFMULCPH the
layout, the per-pair masking and the #UD when the destination is a
source, and VFCMADDCSH is the scalar form.
Rounding inside
Like the other complex instructions, VFCMADDCPH is built from fused multiply-adds: for each part Intel’s optimization manual describes two in a row, starting from the accumulator, with a rounding to FP16 after each (Sections 18.4.3 and 18.5.3). The result is therefore not the correctly rounded value of the whole expression. Intel’s entry lists invalid, overflow, underflow, precision and denormal, sets those flags in MXCSR and runs as if all of them were masked.
In our builds
At -O2 with -march=x86-64-v4 -mavx512fp16, z[i] += x[i] * ~y[i] over
_Complex _Float16 arrays, ~ being the conjugate in GCC and Clang,
stays scalar in both compilers, with a call to the library’s __mulhc3
for a NaN product. With -ffast-math, GCC 14 vectorizes it to
VFCMADDCPH on zmm registers with y read from memory; with only
-fcx-limited-range it uses VFCMULCPH and a separate
VADDPH. Clang 23 uses no complex instruction in these
loops and works on separated real and imaginary parts. A correlation
that sums x[i] * ~y[i] into a single complex value is not vectorized
with VFCMADDCPH by either: GCC builds the products from VMULPH and
VFMADDSUB231PH, Clang from real FMAs, and both
reduce at the end. The intrinsic _mm512_fcmadd_pch(a, b, c) gives
VFCMADDCPH in both, with c as the accumulator.
AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VFCMADDCPH.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VFCMADDCPH xmm {k}{z}, xmm, xmm
VFCMADDCPH_XMM2f16_MASKmskw_XMM2f16_XMM2f16_AVX512 | EVEX.128.F2.MAP6.W0 56 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFCMADDCPH xmm {k}{z}, xmm, m128/m32bcst
VFCMADDCPH_XMM2f16_MASKmskw_XMM2f16_MEM2f16_AVX512 | EVEX.128.F2.MAP6.W0 56 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFCMADDCPH ymm {k}{z}, ymm, ymm
VFCMADDCPH_YMM2f16_MASKmskw_YMM2f16_YMM2f16_AVX512 | EVEX.256.F2.MAP6.W0 56 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFCMADDCPH ymm {k}{z}, ymm, m256/m32bcst
VFCMADDCPH_YMM2f16_MASKmskw_YMM2f16_MEM2f16_AVX512 | EVEX.256.F2.MAP6.W0 56 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VFCMADDCPH zmm {k}{z}, zmm, zmm, {er}
VFCMADDCPH_ZMM2f16_MASKmskw_ZMM2f16_ZMM2f16_AVX512 | EVEX.512.F2.MAP6.W0 56 /r | AVX10.1 or AVX512_FP16 |
VFCMADDCPH zmm {k}{z}, zmm, m512/m32bcst
VFCMADDCPH_ZMM2f16_MASKmskw_ZMM2f16_MEM2f16_AVX512 | EVEX.512.F2.MAP6.W0 56 /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/m32bcstno mask, broadcastymm {k}{z}, ymm, m256/m32bcstno mask, broadcast | xmm {k}{z}, xmm, m128/m32bcstwith a mask, zeroingymm {k}{z}, ymm, m256/m32bcstwith a mask, zeroing | 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/m32bcstno mask, broadcast | zmm {k}{z}, zmm, m512/m32bcstwith a mask, zeroing |
|---|---|---|---|---|---|---|---|---|
| Sapphire Rapids | 9 / 1p01 | 15 / 1p01 | 16 / 1p01 | 21 / 1p01 | 9 / 2p0 | 15 / 2p0 | 16 / 2p0 | 21 / 2p0 |
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 FP16 pair works alike: 4, 8 and 16 FP16 pairs 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 m32bcst, one FP16 pair from memory stands for every element of the last source. The sources are drawn above the result, each element in its own column.
Result FP16 pair i comes from FP16 pair i of xmm1, xmm2 and xmm3. Result FP16 pairs 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
if zmm1.number == zmm2.number:
fault(UD)
if not src3.is_memory:
if zmm1.number == src3.number:
fault(UD)
for i in range(VL // 32):
if k1[i]:
ar = zmm2.f16[2 * i]
ai = zmm2.f16[2 * i + 1]
br = src3.f16[2 * i]
bi = src3.f16[2 * i + 1]
x = zmm1.f16[2 * i]
y = zmm1.f16[2 * i + 1]
x = fmadd(ar, br, x)
y = fmadd(ai, br, y)
x = fmadd(ai, bi, x)
y = fnmadd(ar, bi, y)
zmm1.d[i] = y << 16 | x
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# m32bcst: src3.d[i] is the m32 for every i
# x + y*i += (ar + ai*i)(br - bi*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
# 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 |
|---|---|---|
VFCMADDCPH xmm {k}{z}, xmm, xmm/m128/m32bcst VFCMADDCPH ymm {k}{z}, ymm, ymm/m256/m32bcst VFCMADDCPH zmm {k}{z}, zmm, zmm/m512/m32bcst, {er} | ||
xmm, ymm, zmm | explicit | read, write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | 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-E4
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 VFCMADDCPH, 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_fcmadd_pch
__m128h _mm_fcmadd_pch(__m128h __A, __m128h __B, __m128h __C) |
|
_mm_mask3_fcmadd_pch
__m128h _mm_mask3_fcmadd_pch(__m128h __A, __m128h __B, __m128h __C, __mmask8 __U) |
|
_mm_maskz_fcmadd_pch
__m128h _mm_maskz_fcmadd_pch(__mmask8 __U, __m128h __A, __m128h __B, __m128h __C) |
|
_mm256_fcmadd_pch
__m256h _mm256_fcmadd_pch(__m256h __A, __m256h __B, __m256h __C) |
|
_mm256_mask3_fcmadd_pch
__m256h _mm256_mask3_fcmadd_pch(__m256h __A, __m256h __B, __m256h __C, __mmask8 __U) |
|
_mm256_maskz_fcmadd_pch
__m256h _mm256_maskz_fcmadd_pch(__mmask8 __U, __m256h __A, __m256h __B, __m256h __C) |
|
_mm512_fcmadd_pch
__m512h _mm512_fcmadd_pch(__m512h __A, __m512h __B, __m512h __C) |
|
_mm512_fcmadd_round_pch
__m512h _mm512_fcmadd_round_pch(__m512h A, __m512h B, __m512h C, const int R) |
|
_mm512_mask3_fcmadd_pch
__m512h _mm512_mask3_fcmadd_pch(__m512h __A, __m512h __B, __m512h __C, __mmask16 __U) |
|
_mm512_mask3_fcmadd_round_pch
__m512h _mm512_mask3_fcmadd_round_pch(__m512h A, __m512h B, __m512h C, __mmask16 U, const int R) |
|
_mm512_maskz_fcmadd_pch
__m512h _mm512_maskz_fcmadd_pch(__mmask16 __U, __m512h __A, __m512h __B, __m512h __C) |
|
_mm512_maskz_fcmadd_round_pch
__m512h _mm512_maskz_fcmadd_round_pch(__mmask16 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
- VCVTW2PH
- VDBPSADBW
- VDIVPD
- VDIVPH
- VDIVPS
- VDIVSD
- VDIVSH
- VDIVSS
- VDPBF16PS
- VEXPANDPD
- VEXPANDPS
- VEXTRACTF32X4
- VEXTRACTF32X8
- VEXTRACTF64X2
- VEXTRACTF64X4
- VEXTRACTI32X4
- VEXTRACTI32X8
- VEXTRACTI64X2
- VEXTRACTI64X4
- VEXTRACTPS
- VFCMADDCSH
- VFCMULCPH
- VFCMULCSH
- VFIXUPIMMPD
- VFIXUPIMMPS
- VFIXUPIMMSD
- VFIXUPIMMSS
- VFMADD132PD
- VFMADD132PH
- VFMADD132PS
- VFMADD132SD
- VFMADD132SH
- VFMADD132SS
- VFMADD213PD
- VFMADD213PH
- VFMADD213PS
- VFMADD213SD
- VFMADD213SH
- VFMADD213SS
- VFMADD231PD
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-180 (VFCMADDCPH/
VFMADDCPH) - 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.