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

VGETEXPPH returns the binary exponent of each half as a half, the largest integer e with 2^e no greater than |x|, 32 of them per zmm register. It is VGETEXPPS for halves, and that page covers the rule, the special inputs (a zero gives -infinity, an infinity +infinity, a NaN itself, made quiet) and the use with VGETMANTPH and VSCALEFPH, which split a number and put it back together. The opcode is 42h in EVEX map 6 with the 66 prefix: map 6 repeats the opcodes of the 0F38 map, where VGETEXPPS has the same byte. VADDPH covers the format and the CPUID bits.

Small range, every denormal

The results are few: from 15 for the largest finite halves down to -14 for the smallest normal one, and on to -24 for the smallest denormal, 0001h, since a denormal is normalized first and reported with DE. Every one of these integers is exact as a half. Unlike VGETEXPPS, VGETEXPPH has no DAZ case: FP16 instructions ignore MXCSR.DAZ (Intel’s optimization manual, Section 18.5.4), so a denormal always gives its true exponent, never -infinity. The 512-bit register form takes {sae} to report no flags.

Intel’s optimization manual explains why that matters for halves (Section 18.7): with so narrow a range, denormal inputs are likely in a vectorized FP16 math library, and VGETEXPPH and VGETMANTPH let a logarithm treat them in the main path, as log(x) = VGETEXP(x) × log 2 + log(VGETMANT(x, 8)), with no branch.

In our builds

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 -mavx512fp16 emit VGETEXPPH for _mm512_getexp_ph. logbf on a _Float16, even with -ffast-math, converts it with VCVTSH2SS, calls the library and narrows the result with VCVTSS2SH. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VGETEXPPH.

Forms

Every encoding of VGETEXPPH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VGETEXPPH xmm {k}{z}, xmm VGETEXPPH_XMMf16_MASKmskw_XMMf16_AVX512EVEX.128.66.MAP6.W0 42 /rAVX10.1 or AVX512_FP16 + AVX512VL
VGETEXPPH xmm {k}{z}, m128/m16bcst VGETEXPPH_XMMf16_MASKmskw_MEMf16_AVX512EVEX.128.66.MAP6.W0 42 /rAVX10.1 or AVX512_FP16 + AVX512VL
VGETEXPPH ymm {k}{z}, ymm VGETEXPPH_YMMf16_MASKmskw_YMMf16_AVX512EVEX.256.66.MAP6.W0 42 /rAVX10.1 or AVX512_FP16 + AVX512VL
VGETEXPPH ymm {k}{z}, m256/m16bcst VGETEXPPH_YMMf16_MASKmskw_MEMf16_AVX512EVEX.256.66.MAP6.W0 42 /rAVX10.1 or AVX512_FP16 + AVX512VL
VGETEXPPH zmm {k}{z}, zmm, {sae} VGETEXPPH_ZMMf16_MASKmskw_ZMMf16_AVX512EVEX.512.66.MAP6.W0 42 /rAVX10.1 or AVX512_FP16
VGETEXPPH zmm {k}{z}, m512/m16bcst VGETEXPPH_ZMMf16_MASKmskw_MEMf16_AVX512EVEX.512.66.MAP6.W0 42 /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}, xmmno mask
ymm {k}{z}, ymmno mask
xmm {k}{z}, xmmwith a mask, zeroing
ymm {k}{z}, ymmwith a mask, zeroing
xmm {k}{z}, m128/m16bcst
ymm {k}{z}, m256/m16bcst
zmm {k}{z}, zmm, {sae}no mask, with {sae}zmm {k}{z}, zmm, {sae}with a mask, zeroingzmm {k}{z}, m512/m16bcst
Sapphire Rapids5 / 0.5p016 / 0.5p0112 / 0.5p015 / 1p06 / 1p012 / 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.

Element-wise: each half of the result comes from the half in the same place in each source.
VGETEXPPH: element by elementResult half i comes from half i of xmm2. Result halves 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, r1, r0.01234567xmm2or m128a11111110k1r0r1r2r3r4r5r7xmm1

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. Result halves 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, r1, r0.

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]:
        zmm1.f16[i] = getexp(src2.f16[i])
    elif zeroing:
        zmm1.f16[i] = 0
    # else: zmm1.f16[i] keeps its value
# m16bcst: src2.f16[i] is the m16 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL up

Not run on a processor: none of these processors has AVX512-FP16.

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
VGETEXPPH xmm {k}{z}, xmm/m128/m16bcst VGETEXPPH ymm {k}{z}, ymm/m256/m16bcst VGETEXPPH zmm {k}{z}, zmm/m512/m16bcst, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
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 VGETEXPPH, 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_getexp_ph __m128h _mm_getexp_ph(__m128h __A)

VGETEXPPH xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_mask_getexp_ph __m128h _mm_mask_getexp_ph(__m128h __W, __mmask8 __U, __m128h __A)

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

_mm_maskz_getexp_ph __m128h _mm_maskz_getexp_ph(__mmask8 __U, __m128h __A)

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

_mm256_getexp_ph __m256h _mm256_getexp_ph(__m256h __A)

VGETEXPPH ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_getexp_ph __m256h _mm256_mask_getexp_ph(__m256h __W, __mmask16 __U, __m256h __A)

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

_mm256_maskz_getexp_ph __m256h _mm256_maskz_getexp_ph(__mmask16 __U, __m256h __A)

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

_mm512_getexp_ph __m512h _mm512_getexp_ph(__m512h __A)

VGETEXPPH zmm, zmm EVEX.512 -mavx512fp16

_mm512_getexp_round_ph __m512h _mm512_getexp_round_ph(__m512h A, const int R)

VGETEXPPH zmm, zmm, {sae} EVEX.512 -mavx512fp16

_mm512_mask_getexp_ph __m512h _mm512_mask_getexp_ph(__m512h __W, __mmask32 __U, __m512h __A)

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

_mm512_mask_getexp_round_ph __m512h _mm512_mask_getexp_round_ph(__m512h W, __mmask32 U, __m512h A, const int R)

VGETEXPPH zmm {k}, zmm, {sae} EVEX.512 -mavx512fp16

_mm512_maskz_getexp_ph __m512h _mm512_maskz_getexp_ph(__mmask32 __U, __m512h __A)

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

_mm512_maskz_getexp_round_ph __m512h _mm512_maskz_getexp_round_ph(__mmask32 U, __m512h A, const int R)

VGETEXPPH zmm {k}{z}, zmm, {sae} 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-376 (VGETEXPPH)
  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.