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

VRCP14PS estimates 1/x for each single, with a relative error of at most 2^-14. Only that bound is architectural: the bits of an estimate belong to the processor, so the same input may give different results on Intel and AMD cores. The worst of the 59 results recorded on Zen 5 for this page is 0.8911 times 2^-14. Exact powers of two come back exact; Zen 5 turned 2.0 into 0.5 and 0.5 into 2.0.

It is AVX-512’s successor to RCPPS and VRCPPS, whose bound is 1.5 times 2^-12, about six times looser, and which have no zmm form, no masking and no double version; VRCP14PD is the double one.

Special inputs and flags

A zero gives an infinity of its sign, an infinity a zero of its sign, and a NaN comes back quiet. The instruction sets no MXCSR flag at all, not even for an SNaN: Zen 5 quieted 7F812345h to 7FC12345h and left MXCSR as it was. Denormals follow DAZ and FTZ: under DAZ a denormal input counts as a zero, and the inputs above 2^126 have reciprocals below the normal range, which Zen 5 returned as denormals (the largest single gave 00200000h) and, under FTZ, as zeros.

Division and Newton-Raphson

One Newton-Raphson step, r’ = r(2 - xr), roughly doubles the correct bits, so VRCP14PS plus one step comes close to single precision. Intel’s optimization manual recommends that sequence where throughput matters more than full precision, and notes that doubles need two steps from VRCP14PD instead of three from older estimates (Sections 17.15.1 and 17.25).

Compilers do this for division under -ffast-math. For a loop of a[i] / b[i] with -march=x86-64-v4, GCC 14 at -O2 emits VRCP14PS on zmm registers, one Newton step and a multiplication by a[i]; Clang 23 does the same with -march=znver5, the step done with VFNMADD213PS, but with -march=x86-64-v4 it uses VRCPPS on ymm registers. Since the step starts from the processor’s estimate, such a quotient can differ in its last bit between processors, where VDIVPS always gives the correctly rounded result.

AMD’s Zen 5 guide lists VRCP14PS as one macro-op with a latency of 5 cycles, against 4 for VRCPPS.

Forms

Every encoding of VRCP14PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VRCP14PS zmm {k}{z}, zmm VRCP14PS_ZMMf32_MASKmskw_ZMMf32_AVX512EVEX.512.66.0F38.W0 4C /rAVX10.1 or AVX512F
VRCP14PS zmm {k}{z}, m512/m32bcst VRCP14PS_ZMMf32_MASKmskw_MEMf32_AVX512EVEX.512.66.0F38.W0 4C /rAVX10.1 or AVX512F
VRCP14PS xmm {k}{z}, xmm VRCP14PS_XMMf32_MASKmskw_XMMf32_AVX512EVEX.128.66.0F38.W0 4C /rAVX10.1 or AVX512F + AVX512VL
VRCP14PS xmm {k}{z}, m128/m32bcst VRCP14PS_XMMf32_MASKmskw_MEMf32_AVX512EVEX.128.66.0F38.W0 4C /rAVX10.1 or AVX512F + AVX512VL
VRCP14PS ymm {k}{z}, ymm VRCP14PS_YMMf32_MASKmskw_YMMf32_AVX512EVEX.256.66.0F38.W0 4C /rAVX10.1 or AVX512F + AVX512VL
VRCP14PS ymm {k}{z}, m256/m32bcst VRCP14PS_YMMf32_MASKmskw_MEMf32_AVX512EVEX.256.66.0F38.W0 4C /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}, zmmzmm {k}{z}, m512/m32bcstxmm {k}{z}, xmmxmm {k}{z}, m128/m32bcstymm {k}{z}, ymmymm {k}{z}, m256/m32bcst
Skylake-SP, Ice Lake4 / 2p0511 / 2p054 / 1p010 / 1p04 / 1p011 / 1p0
Sapphire Rapids7 / 2p0514 / 2p054 / 1p011 / 1p04 / 1p012 / 1p0
Zen 45 / 1FP0 FP112 / 1FP0 FP14 / 0.51FP0 FP111 / 0.5FP0 FP15 / 0.5FP0 FP112 / 0.5FP0 FP1
  1. Zen 4 model: AMD's spreadsheets give latency 5 for Zen 4 and Zen 5 (AMD 57647, row 3198; AMD 58455, row 884).

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.
VRCP14PS: 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] = rcp14(src2.f32[i])
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# rcp14: 1/a within 2^-14; Zen 5's 59
# recorded results: 0.8911 * 2^-14 at most
# denormals and tiny results by MXCSR.DAZ and FTZ; no flags
# m32bcst: src2.f32[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 19 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
VRCP14PS xmm {k}{z}, xmm/m128/m32bcst VRCP14PS ymm {k}{z}, ymm/m256/m32bcst VRCP14PS zmm {k}{z}, zmm/m512/m32bcst
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-E4

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 VRCP14PS, 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_rcp14_ps __m128 _mm_rcp14_ps(__m128 __A)

VRCP14PS xmm, xmm EVEX.128 -mavx512vl

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

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

_mm_maskz_rcp14_ps __m128 _mm_maskz_rcp14_ps(__mmask8 __U, __m128 __A)

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

_mm256_rcp14_ps __m256 _mm256_rcp14_ps(__m256 __A)

VRCP14PS ymm, ymm EVEX.256 -mavx512vl

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

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

_mm256_maskz_rcp14_ps __m256 _mm256_maskz_rcp14_ps(__mmask8 __U, __m256 __A)

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

_mm512_rcp14_ps __m512 _mm512_rcp14_ps(__m512 __A)

VRCP14PS zmm, zmm EVEX.512 -mavx512f

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

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

_mm512_maskz_rcp14_ps __m512 _mm512_maskz_rcp14_ps(__mmask16 __U, __m512 __A)

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