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

VRCPPH estimates 1/x for each half, 32 per zmm register, with a relative error below 2^-11 + 2^-14 by Intel’s manual. That is hardly more than the rounding error of a half, which has 11 significant bits: the estimate is nearly the correctly rounded reciprocal, where VRCP14PS for singles is good to 14 of 24 bits and needs a Newton-Raphson step. The opcode is 4Ch in EVEX map 6 with the 66 prefix, VRCP14PS’s byte in 0F38; it takes no rounding mode, sets no MXCSR flag and raises no SIMD exception. VADDPH covers the format and the CPUID bits.

No Newton step

Intel’s optimization manual puts numbers on it (Sections 18.5.8.1 and 18.5.8.2): VRCPPH is within 0.5 ULP for 98% of inputs and within 0.5625 ULP for the rest, so a Newton step would gain nothing. On the processor it describes it takes 4 cycles at up to 256 bits and 6 at 512, against 15 and 24 for a division by VDIVPH, and a quotient taken as a times VRCPPH(b) is about three times faster than the division and within about 1.5 ULP, except for divisors near either end of the range.

Intel’s table of special inputs maps exact powers of two to exact powers of two and the infinities to zeros of their sign. Denormals are handled, not flushed: only those up to 2^-16 give infinity, since their reciprocals pass 65504; the larger denormals have a finite reciprocal.

In our builds

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 -mavx512fp16 keep 1 / a[i] over _Float16 arrays a VDIVPH. With -ffast-math both replace it by VRCPPH alone, and a[i] / b[i] by VRCPPH and VMULPH, with no refinement step, unlike the float loops on VRCP14PS’s page. On a single value with -ffast-math, Clang emits VRCPSH and GCC keeps VDIVSH. The intrinsic _mm512_rcp_ph gives it in both. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VRCPPH.

Forms

Every encoding of VRCPPH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VRCPPH xmm {k}{z}, xmm VRCPPH_XMMf16_MASKmskw_XMMf16_AVX512EVEX.128.66.MAP6.W0 4C /rAVX10.1 or AVX512_FP16 + AVX512VL
VRCPPH xmm {k}{z}, m128/m16bcst VRCPPH_XMMf16_MASKmskw_MEMf16_AVX512EVEX.128.66.MAP6.W0 4C /rAVX10.1 or AVX512_FP16 + AVX512VL
VRCPPH ymm {k}{z}, ymm VRCPPH_YMMf16_MASKmskw_YMMf16_AVX512EVEX.256.66.MAP6.W0 4C /rAVX10.1 or AVX512_FP16 + AVX512VL
VRCPPH ymm {k}{z}, m256/m16bcst VRCPPH_YMMf16_MASKmskw_MEMf16_AVX512EVEX.256.66.MAP6.W0 4C /rAVX10.1 or AVX512_FP16 + AVX512VL
VRCPPH zmm {k}{z}, zmm VRCPPH_ZMMf16_MASKmskw_ZMMf16_AVX512EVEX.512.66.MAP6.W0 4C /rAVX10.1 or AVX512_FP16
VRCPPH zmm {k}{z}, m512/m16bcst VRCPPH_ZMMf16_MASKmskw_MEMf16_AVX512EVEX.512.66.MAP6.W0 4C /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
ymm {k}{z}, ymm
xmm {k}{z}, m128/m16bcstymm {k}{z}, m256/m16bcstzmm {k}{z}, zmmno maskzmm {k}{z}, zmmwith a mask, zeroingzmm {k}{z}, m512/m16bcstno mask, broadcastzmm {k}{z}, m512/m16bcstwith a mask, zeroing
Sapphire Rapids4 / 1p011 / 1p012 / 1p07 / 2p059 / 2p0514 / 2p0516 / 2p05

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.
VRCPPH: 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] = rcp(src2.f16[i])
    elif zeroing:
        zmm1.f16[i] = 0
    # else: zmm1.f16[i] keeps its value
# rcp: 1/a within 2^-11 + 2^-14; denormals kept; no flags
# m16bcst: src2.f16[i] is the m16 for every i
# 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
VRCPPH xmm {k}{z}, xmm/m128/m16bcst VRCPPH ymm {k}{z}, ymm/m256/m16bcst VRCPPH zmm {k}{z}, zmm/m512/m16bcst
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-E4

Attributes

What else XED records about the forms. How to read.

All forms
write masking
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VRCPPH, 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_rcp_ph __m128h _mm_rcp_ph(__m128h __A)

VRCPPH xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

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

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

_mm_maskz_rcp_ph __m128h _mm_maskz_rcp_ph(__mmask8 __U, __m128h __A)

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

_mm256_rcp_ph __m256h _mm256_rcp_ph(__m256h __A)

VRCPPH ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

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

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

_mm256_maskz_rcp_ph __m256h _mm256_maskz_rcp_ph(__mmask16 __U, __m256h __A)

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

_mm512_rcp_ph __m512h _mm512_rcp_ph(__m512h __A)

VRCPPH zmm, zmm EVEX.512 -mavx512fp16

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

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

_mm512_maskz_rcp_ph __m512h _mm512_maskz_rcp_ph(__mmask32 __U, __m512h __A)

VRCPPH zmm {k}{z}, zmm 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-682 (VRCPPH)
  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.