Instruction
VADDPH
Adds packed half-precision values.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VADDPH adds half-precision values (IEEE 754’s binary16: a sign, 5 exponent bits and 10 fraction bits) element by element, 32 of them in a zmm register, twice as many as VADDPS. It is the plainest instruction of AVX512-FP16, which brought arithmetic to a format that F16C had only converted: before it, halves were widened to singles with VCVTPH2PS, added, and narrowed again. VADDSH adds the lowest element only.
Requirements and encoding
The 512-bit form needs AVX512_FP16 (CPUID leaf 7, EDX bit 23), the xmm
and ymm forms AVX512VL as well; Intel’s manual adds that AVX512-FP16
requires AVX512BW, whose instructions handle the 32-bit masks. AVX10.1
includes all of it. The FP16 instructions live in two new EVEX opcode
maps, 5 and 6, so VADDPH is EVEX.MAP5 58h, the opcode byte of ADDPS in
another map. Only the 512-bit register form takes a rounding mode in the
instruction ({er}): AVX10.2 at first allowed it for ymm too, and
revision 4.0 of its specification withdrew that.
A narrow range
The largest finite half is 65504, the smallest normal one 2^-14, and
only integers up to 2048 are all exact. Intel’s optimization manual
warns that 16-bit integers converted to halves land near the top of that
range, where almost any arithmetic overflows to infinity, and suggests
scaling them by a constant such as 1/256 (Section 18.5.7). Denormals
cost nothing: the same chapter says FP16 arithmetic handles them at full
speed and ignores MXCSR.DAZ and MXCSR.FTZ (Section 18.5.4). Those two
bits are all it ignores: without {er}, VADDPH rounds as MXCSR.RC says
and sets MXCSR’s exception flags, the denormal flag among them, as
Intel’s page for the instruction lists. Complex numbers need no
instruction of their own for adding: the real and imaginary parts are
added as separate halves.
In compiled code
With -march=sapphirerapids, Clang 23 at -O2 vectorizes
c[i] = a[i] + b[i] over _Float16 arrays into VADDPH on ymm
registers, with one operand from memory, checking at run time that
pointer parameters do not overlap. GCC 14 does the same at -O2 only when
the arrays cannot overlap and a constant count leaves no remainder:
1,024 elements of global arrays or through restrict pointers. Pointers
without restrict keep its loop on VADDSH, one element at a time, 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, with
an overlap check where it needs one and VADDSH for the remainder.
Without AVX512-FP16, as with -march=znver5, both compilers convert
each operand with VCVTPH2PS, add singles and narrow the sum with
VCVTPS2PH; the page’s processor table shows which
processors report the extension.
In the optimization guide
What the optimization guide says about VADDPH, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Golden Cove and Raptor Cove
- Vectors, AVX-512 and AMX: AVX-512 FP16 adds and multiplies 32 half-precision values per 512-bit register with a latency of four cycles; division and square root take about 31. sources differ
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VADDPH xmm {k}{z}, xmm, xmm
VADDPH_XMMf16_MASKmskw_XMMf16_XMMf16_AVX512 | EVEX.128.NP.MAP5.W0 58 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VADDPH xmm {k}{z}, xmm, m128/m16bcst
VADDPH_XMMf16_MASKmskw_XMMf16_MEMf16_AVX512 | EVEX.128.NP.MAP5.W0 58 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VADDPH ymm {k}{z}, ymm, ymm
VADDPH_YMMf16_MASKmskw_YMMf16_YMMf16_AVX512 | EVEX.256.NP.MAP5.W0 58 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VADDPH ymm {k}{z}, ymm, m256/m16bcst
VADDPH_YMMf16_MASKmskw_YMMf16_MEMf16_AVX512 | EVEX.256.NP.MAP5.W0 58 /r | AVX10.1 or AVX512_FP16 + AVX512VL |
VADDPH zmm {k}{z}, zmm, zmm, {er}
VADDPH_ZMMf16_MASKmskw_ZMMf16_ZMMf16_AVX512 | EVEX.512.NP.MAP5.W0 58 /r | AVX10.1 or AVX512_FP16 |
VADDPH zmm {k}{z}, zmm, m512/m16bcst
VADDPH_ZMMf16_MASKmskw_ZMMf16_MEMf16_AVX512 | EVEX.512.NP.MAP5.W0 58 /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.
Result half i comes from half i of xmm2 and xmm3. Result halves 7 to 0: a7+b7, unchanged (bit 6 of k1 is 0), a5+b5, a4+b4, a3+b3, a2+b2, a1+b1, a0+b0.
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 = zmm2.f16[i]
b = src3.f16[i]
zmm1.f16[i] = add(a, 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 upNot run on a processor: none of these processors has AVX512-FP16. The tests check its arithmetic against MPFR.
Operands
| Operand | Kind | Action |
|---|---|---|
VADDPH xmm {k}{z}, xmm, xmm/m128/m16bcst VADDPH ymm {k}{z}, ymm, ymm/m256/m16bcst VADDPH zmm {k}{z}, zmm, zmm/m512/m16bcst, {er} | ||
xmm, ymm, zmm | explicit | 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 VADDPH, 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_add_ph
__m128h _mm_add_ph(__m128h __A, __m128h __B) |
|
_mm_mask_add_ph
__m128h _mm_mask_add_ph(__m128h __W, __mmask8 __U, __m128h __A, __m128h __B) |
|
_mm_maskz_add_ph
__m128h _mm_maskz_add_ph(__mmask8 __U, __m128h __A, __m128h __B) |
|
_mm256_add_ph
__m256h _mm256_add_ph(__m256h __A, __m256h __B) |
|
_mm256_mask_add_ph
__m256h _mm256_mask_add_ph(__m256h __W, __mmask16 __U, __m256h __A, __m256h __B) |
|
_mm256_maskz_add_ph
__m256h _mm256_maskz_add_ph(__mmask16 __U, __m256h __A, __m256h __B) |
|
_mm512_add_ph
__m512h _mm512_add_ph(__m512h __A, __m512h __B) |
|
_mm512_add_round_ph
__m512h _mm512_add_round_ph(__m512h A, __m512h B, const int R) |
|
_mm512_mask_add_ph
__m512h _mm512_mask_add_ph(__m512h __W, __mmask32 __U, __m512h __A, __m512h __B) |
|
_mm512_mask_add_round_ph
__m512h _mm512_mask_add_round_ph(__m512h W, __mmask32 U, __m512h A, __m512h B, const int R) |
|
_mm512_maskz_add_ph
__m512h _mm512_maskz_add_ph(__mmask32 __U, __m512h __A, __m512h __B) |
|
_mm512_maskz_add_round_ph
__m512h _mm512_maskz_add_round_ph(__mmask32 U, __m512h A, __m512h B, 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
- KSHIFTRB
- KSHIFTRD
- KSHIFTRQ
- KSHIFTRW
- KTESTB
- KTESTD
- KTESTQ
- KTESTW
- KUNPCKBW
- KUNPCKDQ
- KUNPCKWD
- KXNORB
- KXNORD
- KXNORQ
- KXNORW
- KXORB
- KXORD
- KXORQ
- KXORW
- VADDPD
- VADDPS
- VADDSD
- VADDSH
- VADDSS
- VAESDEC
- VAESDECLAST
- VAESENC
- VAESENCLAST
- VALIGND
- VALIGNQ
- VANDNPD
- VANDNPS
- VANDPD
- VANDPS
- VBLENDMPD
- VBLENDMPS
- VBROADCASTF32X2
- VBROADCASTF32X4
- VBROADCASTF32X8
- VBROADCASTF64X2
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-1 (VADDPH)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- 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.