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

VGETEXPPS returns the binary exponent of each single as a single: the largest integer e with 2^e no greater than |x|, so 8 gives 3.0, 0.75 gives -1.0 and 1e30 gives 99.0. The sign of x does not matter. It is C’s logbf for every finite nonzero input, done on a whole vector without touching the bits by hand: shifting the exponent field out with an integer shift gives the wrong answer for denormals and needs the special values sorted out separately.

Special inputs

InputResult
+0 or -0-infinity
+infinity or -infinity+infinity
NaNthe NaN, quiet; IE for an SNaN
denormalits true exponent, -127 to -149, with DE
denormal under DAZ-infinity, as a zero

Zen 5 recorded each row: the smallest denormal gave -149.0 and 007FFFFFh gave -127.0, with MXCSR’s DE flag set, and with DAZ both gave -infinity. A zero raises no divide-by-zero flag here, where logbf(0) does. The register form of the zmm version takes {sae} to report no flags at all.

With VGETMANTPS and VSCALEFPS

VGETMANTPS returns the other half of the number, its significand normalized to an interval the immediate chooses, so that x equals the significand times 2 to the exponent, and VSCALEFPS puts the two back together. The x87 instruction FXTRACT splits a number the same way in one step. Intel’s optimization manual builds logarithms on the split (Section 17.15.2): log2(x) is VGETEXP(x) plus log2 of the significand in [1, 2), which a short polynomial or a table covers, and the reverse pairing with VSCALEF gives a division without branches for overflow, underflow or special inputs (Section 17.15.5).

Neither GCC 14 nor Clang 23 at -O2 turns logbf into VGETEXPPS, even with -ffast-math: both call the library function. The instruction comes from the intrinsics _mm512_getexp_ps and their kin.

AMD’s Zen 5 guide lists VGETEXPPS as one macro-op with a latency of 3 cycles, the same as VGETMANTPS.

Forms

Every encoding of VGETEXPPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VGETEXPPS zmm {k}{z}, zmm, {sae} VGETEXPPS_ZMMf32_MASKmskw_ZMMf32_AVX512EVEX.512.66.0F38.W0 42 /rAVX10.1 or AVX512F
VGETEXPPS zmm {k}{z}, m512/m32bcst VGETEXPPS_ZMMf32_MASKmskw_MEMf32_AVX512EVEX.512.66.0F38.W0 42 /rAVX10.1 or AVX512F
VGETEXPPS xmm {k}{z}, xmm VGETEXPPS_XMMf32_MASKmskw_XMMf32_AVX512EVEX.128.66.0F38.W0 42 /rAVX10.1 or AVX512F + AVX512VL
VGETEXPPS xmm {k}{z}, m128/m32bcst VGETEXPPS_XMMf32_MASKmskw_MEMf32_AVX512EVEX.128.66.0F38.W0 42 /rAVX10.1 or AVX512F + AVX512VL
VGETEXPPS ymm {k}{z}, ymm VGETEXPPS_YMMf32_MASKmskw_YMMf32_AVX512EVEX.256.66.0F38.W0 42 /rAVX10.1 or AVX512F + AVX512VL
VGETEXPPS ymm {k}{z}, m256/m32bcst VGETEXPPS_YMMf32_MASKmskw_MEMf32_AVX512EVEX.256.66.0F38.W0 42 /rAVX10.1 or AVX512F + AVX512VL

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.
Modelzmm {k}{z}, zmm, {sae}zmm {k}{z}, m512/m32bcstxmm {k}{z}, xmm
ymm {k}{z}, ymm
xmm {k}{z}, m128/m32bcstymm {k}{z}, m256/m32bcst
Skylake-SP, Ice Lake8 / 1p0515 / 1p058 / 1p0114 / 1p0115 / 1p01
Sapphire Rapids4 / 1p012 / 1p04 / 0.5p0111 / 0.5p0112 / 0.5p01
Zen 43 / 1FP2 FP310 / 1FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP310 / 0.5FP2 FP3

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 single of the result comes from the single in the same place in each source.
VGETEXPPS: element by elementResult single i comes from single i of xmm2. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2or m128a1110k1r0r1r3xmm1

Every single works alike: 4, 8 and 16 singles 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 single from memory stands for every element of the last source.

Result single i comes from single i of xmm2. Result singles 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.

for i in range(VL // 32):
    if k1[i]:
        zmm1.f32[i] = getexp(src2.f32[i])
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# m32bcst: src2.f32[i] is the m32 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 33 cases.

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
VGETEXPPS xmm {k}{z}, xmm/m128/m32bcst VGETEXPPS ymm {k}{z}, ymm/m256/m32bcst VGETEXPPS zmm {k}{z}, zmm/m512/m32bcst, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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 VGETEXPPS, 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_ps __m128 _mm_getexp_ps(__m128 __A)

VGETEXPPS xmm, xmm EVEX.128 -mavx512vl

_mm_mask_getexp_ps __m128 _mm_mask_getexp_ps(__m128 __W, __mmask8 __U, __m128 __A)

VGETEXPPS xmm {k}, xmm EVEX.128 -mavx512vl

_mm_maskz_getexp_ps __m128 _mm_maskz_getexp_ps(__mmask8 __U, __m128 __A)

VGETEXPPS xmm {k}{z}, xmm EVEX.128 -mavx512vl

_mm256_getexp_ps __m256 _mm256_getexp_ps(__m256 __A)

VGETEXPPS ymm, ymm EVEX.256 -mavx512vl

_mm256_mask_getexp_ps __m256 _mm256_mask_getexp_ps(__m256 __W, __mmask8 __U, __m256 __A)

VGETEXPPS ymm {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_getexp_ps __m256 _mm256_maskz_getexp_ps(__mmask8 __U, __m256 __A)

VGETEXPPS ymm {k}{z}, ymm EVEX.256 -mavx512vl

_mm512_getexp_ps __m512 _mm512_getexp_ps(__m512 __A)

VGETEXPPS zmm, zmm EVEX.512 -mavx512f

_mm512_getexp_round_ps __m512 _mm512_getexp_round_ps(__m512 A, const int R)

VGETEXPPS zmm, zmm, {sae} EVEX.512 -mavx512f

_mm512_mask_getexp_ps __m512 _mm512_mask_getexp_ps(__m512 __W, __mmask16 __U, __m512 __A)

VGETEXPPS zmm {k}, zmm EVEX.512 -mavx512f

_mm512_mask_getexp_round_ps __m512 _mm512_mask_getexp_round_ps(__m512 W, __mmask16 U, __m512 A, const int R)

VGETEXPPS zmm {k}, zmm, {sae} EVEX.512 -mavx512f

_mm512_maskz_getexp_ps __m512 _mm512_maskz_getexp_ps(__mmask16 __U, __m512 __A)

VGETEXPPS zmm {k}{z}, zmm EVEX.512 -mavx512f

_mm512_maskz_getexp_round_ps __m512 _mm512_maskz_getexp_round_ps(__mmask16 U, __m512 A, const int R)

VGETEXPPS zmm {k}{z}, zmm, {sae} EVEX.512 -mavx512f

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
AVX512F_512

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

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512F_128

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

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512F_256
Same as AVX512F_128Same as AVX512F_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-379 (VGETEXPPS)
  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.