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

VDIVPH divides the halves of its first source by those of the second, element by element, 32 per zmm register, and rounds each quotient correctly under MXCSR.RC, or under {er} on the 512-bit register form. It is VDIVPS for half precision, opcode 5Eh in EVEX map 5, and reports invalid, divide by zero, overflow, underflow, precision and denormal. VADDPH covers the format, the CPUID bits and the encoding; VDIVSH divides the low element only.

Division or reciprocal

Division is the slow one among the FP16 operations: Intel’s optimization manual gives it about 24 cycles of latency at 512 bits, one every 16 cycles. For halves, the reciprocal estimate of VRCPPH is close enough to need no Newton-Raphson step, and the manual shows that a VRCPPH followed by VMULPH is about three times faster than VDIVPH, with 98% of quotients within 0.5625 ULP when both operands lie in the middle of the range and none worse than about 1.5 ULP, failing only for divisors near the denormals or the largest exponents (Section 18.5.8.2). The two give different results, so a compiler may substitute one for the other only when told it may.

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, GCC 14 and Clang 23 vectorize c[i] = a[i] / b[i] over global _Float16 arrays to VDIVPH, GCC on zmm and Clang on ymm registers, as well as 1 / a[i] and a[i] / 3. With -ffast-math both switch: the quotient becomes VRCPPH and VMULPH, the reciprocal VRCPPH alone, and the division by 3 a multiplication by the rounded constant 1/3. With that option the scalar x / y stays VDIVSH in GCC and becomes VRCPSH and VMULSH in Clang.

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

In the optimization guide

What the optimization guide says about VDIVPH, 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

Every encoding of VDIVPH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VDIVPH xmm {k}{z}, xmm, xmm VDIVPH_XMMf16_MASKmskw_XMMf16_XMMf16_AVX512EVEX.128.NP.MAP5.W0 5E /rAVX10.1 or AVX512_FP16 + AVX512VL
VDIVPH xmm {k}{z}, xmm, m128/m16bcst VDIVPH_XMMf16_MASKmskw_XMMf16_MEMf16_AVX512EVEX.128.NP.MAP5.W0 5E /rAVX10.1 or AVX512_FP16 + AVX512VL
VDIVPH ymm {k}{z}, ymm, ymm VDIVPH_YMMf16_MASKmskw_YMMf16_YMMf16_AVX512EVEX.256.NP.MAP5.W0 5E /rAVX10.1 or AVX512_FP16 + AVX512VL
VDIVPH ymm {k}{z}, ymm, m256/m16bcst VDIVPH_YMMf16_MASKmskw_YMMf16_MEMf16_AVX512EVEX.256.NP.MAP5.W0 5E /rAVX10.1 or AVX512_FP16 + AVX512VL
VDIVPH zmm {k}{z}, zmm, zmm, {er} VDIVPH_ZMMf16_MASKmskw_ZMMf16_ZMMf16_AVX512EVEX.512.NP.MAP5.W0 5E /rAVX10.1 or AVX512_FP16
VDIVPH zmm {k}{z}, zmm, m512/m16bcst VDIVPH_ZMMf16_MASKmskw_ZMMf16_MEMf16_AVX512EVEX.512.NP.MAP5.W0 5E /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, xmmno mask
ymm {k}{z}, ymm, ymmno mask
xmm {k}{z}, xmm, xmmwith a mask, zeroing
ymm {k}{z}, ymm, ymmwith a mask
xmm {k}{z}, xmm, m128/m16bcstno mask, broadcastxmm {k}{z}, xmm, m128/m16bcstwith a mask, zeroingymm {k}{z}, ymm, ymmzeroingymm {k}{z}, ymm, m256/m16bcstno mask, broadcastymm {k}{z}, ymm, m256/m16bcstwith a mask, zeroingzmm {k}{z}, zmm, zmm, {er}no mask, with {er}zmm {k}{z}, zmm, zmm, {er}with a mask, zeroingzmm {k}{z}, zmm, m512/m16bcstno mask, broadcastzmm {k}{z}, zmm, m512/m16bcstwith a mask, zeroing
Sapphire Rapids31 / 2p01533 / 2p01536 / 2p01538 / 2p01511 / 2p01537 / 2p01539 / 2p01541 / 4p05643 / 4p05649 / 4p05651 / 4p056

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.

Element-wise: each half of the result comes from the half in the same place in each source.
VDIVPH: element by elementResult 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.01234567xmm2a11111110k1a0/b0a1/b1a2/b2a3/b3a4/b4a5/b5a7/b7xmm101234567xmm3or m128b

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] = div(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 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
VDIVPH xmm {k}{z}, xmm, xmm/m128/m16bcst VDIVPH ymm {k}{z}, ymm, ymm/m256/m16bcst VDIVPH zmm {k}{z}, zmm, zmm/m512/m16bcst, {er}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m16bcst, ymm/m256/m16bcst, zmm/m512/m16bcstexplicitread

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 VDIVPH, 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_div_ph __m128h _mm_div_ph(__m128h __A, __m128h __B)

VDIVPH xmm, xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

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

VDIVPH xmm {k}, xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

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

VDIVPH xmm {k}{z}, xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm256_div_ph __m256h _mm256_div_ph(__m256h __A, __m256h __B)

VDIVPH ymm, ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_div_ph __m256h _mm256_mask_div_ph(__m256h __W, __mmask16 __U, __m256h __A, __m256h __B)

VDIVPH ymm {k}, ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_maskz_div_ph __m256h _mm256_maskz_div_ph(__mmask16 __U, __m256h __A, __m256h __B)

VDIVPH ymm {k}{z}, ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm512_div_ph __m512h _mm512_div_ph(__m512h __A, __m512h __B)

VDIVPH zmm, zmm, zmm EVEX.512 -mavx512fp16

_mm512_div_round_ph __m512h _mm512_div_round_ph(__m512h A, __m512h B, const int R)

VDIVPH zmm, zmm, zmm, {er} EVEX.512 -mavx512fp16

_mm512_mask_div_ph __m512h _mm512_mask_div_ph(__m512h __W, __mmask32 __U, __m512h __A, __m512h __B)

VDIVPH zmm {k}, zmm, zmm EVEX.512 -mavx512fp16

_mm512_mask_div_round_ph __m512h _mm512_mask_div_round_ph(__m512h W, __mmask32 U, __m512h A, __m512h B, const int R)

VDIVPH zmm {k}, zmm, zmm, {er} EVEX.512 -mavx512fp16

_mm512_maskz_div_ph __m512h _mm512_maskz_div_ph(__mmask32 __U, __m512h __A, __m512h __B)

VDIVPH zmm {k}{z}, zmm, zmm EVEX.512 -mavx512fp16

_mm512_maskz_div_round_ph __m512h _mm512_maskz_div_round_ph(__mmask32 U, __m512h A, __m512h B, const int R)

VDIVPH zmm {k}{z}, zmm, zmm, {er} EVEX.512 -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_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512_FP16 + AVX512VL
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6
AVX512_FP16_256
Same as AVX512_FP16_128Same as AVX512_FP16_128
AVX512_FP16_512

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

Same as AVX512_FP16_128

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-157 (VDIVPH)
  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.