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

Forms

Every encoding of VRCP28PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VRCP28PS zmm {k}{z}, zmm, {sae} VRCP28PS_ZMMf32_MASKmskw_ZMMf32_AVX512EREVEX.512.66.0F38.W0 CA /rAVX512ER
VRCP28PS zmm {k}{z}, m512/m32bcst VRCP28PS_ZMMf32_MASKmskw_MEMf32_AVX512EREVEX.512.66.0F38.W0 CA /rAVX512ER

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.
VRCP28PS: element by elementResult single i comes from single i of zmm2. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123zmm2or m512a1110k1r0r1r3zmm1

Every single works alike: 16 singles in the zmm form. 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 zmm2. 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.

if not cpuid_leaf(7, 0)[1] >> 27 & 1:
    fault(UD)                    # CPUID: no AVX512ER
for i in range(16):
    if k1[i]:
        zmm1.f32[i] = rcp28(src2.f32[i])
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# rcp28: 1/a within 2^-28, rounded to a single
# denormals are zeros and tiny results zeros, whatever MXCSR
# says; IE for an SNaN, ZE for a zero
# m32bcst: src2.f32[i] is the m32 for every i
# {sae}: no exception flags

Run on AMD Zen 5 (EPYC 9645): 2 cases. Its cases ran where CPUID reported no AVX512ER, and every one raised an exception.

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
VRCP28PS zmm {k}{z}, zmm/m512/m32bcst, {sae}
zmmexplicitwrite (masked)
{k}explicitread (write mask)
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

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
AVX512ER_512

AVX512ER
CPUID.(EAX=07H,ECX=0):EBX[27] AVX512ER

Knights Landing, Knights Mill

More AVX512ER 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. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2D, page 8-24 (VRCP28PS)
  3. Intel Xeon Phi Coprocessor Instruction Set Architecture Reference Manual (327364-001, September 2012)

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 text is our own.