Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VGF2P8AFFINEINVQB is GF2P8AFFINEINVQB in VEX and EVEX encodings: each byte is replaced by its inverse in GF(2^8), multiplied by the 8-by-8 bit matrix in the matching quadword of the second source, and XORed with the immediate. That page covers the field, the inverse and AES’s S-box, and GF2P8AFFINEQB the layout of the matrix. The new encodings add a separate destination, zeroed above the vector length, a memory operand at any alignment, and wider vectors:

  • The VEX forms, on xmm and ymm registers, need GFNI and AVX, not AVX-512.
  • The EVEX forms need GFNI with AVX512VL below 512 bits, AVX512F at 512 bits, or AVX10.1. Their write mask selects bytes, but their broadcast repeats a quadword: one matrix for every group of eight bytes.
  • The EVEX forms belong to exception class E4NF, without fault suppression: a memory operand is read in full whatever the mask.

On Zen 5

vgf2p8affineinvqb zmm17, zmm30, qword bcst [mem], 0 broadcast the identity matrix 0102040810204080h to all eight quadwords, which leaves the plain inverse: 02h became 8Dh, 80h became 83h, FFh became 1Ch, 53h and CAh swapped, and 00h stayed 00h, as the SDM’s table lists. With AES’s matrix F1E3C78F1F3E7CF8h in its third quadword and an immediate of 63h, {evex} vgf2p8affineinvqb zmm1, zmm2, zmmword ptr [mem], 0x63 turned 00h, 01h, 53h and FFh into 63h, 7Ch, EDh and 16h, their S-box values in FIPS-197; a zero quadword in the matrix gave 63h for each of its bytes, the immediate alone.

In our builds

GCC 14 and Clang 23 at -O2 emit it only for the intrinsics, which need -mgfni on top of -mavx2 or an x86-64 level: both reject them with -march=x86-64-v4 alone and accept them with -march=znver5. An S-box loop over _mm256_gf2p8affineinv_epi64_epi8 keeps the VEX form even with -march=x86-64-v4 -mgfni; the _mm512_ and masked intrinsics give EVEX. Both compilers keep the matrix in a register: GCC loads it as a full vector constant, Clang with a VPBROADCASTQ of one quadword.

AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows alike a latency of 3 cycles, two per cycle on pipes FP1 and FP2.

Forms

Every encoding of VGF2P8AFFINEINVQB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VGF2P8AFFINEINVQB xmm, xmm, xmm, imm8 VGF2P8AFFINEINVQB_XMMu8_XMMu8_XMMu64_IMM8VEX.128.66.0F3A.W1 CF /r ibGFNI + AVX
VGF2P8AFFINEINVQB xmm, xmm, m128, imm8 VGF2P8AFFINEINVQB_XMMu8_XMMu8_MEMu64_IMM8VEX.128.66.0F3A.W1 CF /r ibGFNI + AVX
VGF2P8AFFINEINVQB ymm, ymm, ymm, imm8 VGF2P8AFFINEINVQB_YMMu8_YMMu8_YMMu64_IMM8VEX.256.66.0F3A.W1 CF /r ibGFNI + AVX
VGF2P8AFFINEINVQB ymm, ymm, m256, imm8 VGF2P8AFFINEINVQB_YMMu8_YMMu8_MEMu64_IMM8VEX.256.66.0F3A.W1 CF /r ibGFNI + AVX
VGF2P8AFFINEINVQB xmm {k}{z}, xmm, xmm, imm8 VGF2P8AFFINEINVQB_XMMu8_MASKmskw_XMMu8_XMMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 CF /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEINVQB xmm {k}{z}, xmm, m128/m64bcst, imm8 VGF2P8AFFINEINVQB_XMMu8_MASKmskw_XMMu8_MEMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 CF /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEINVQB ymm {k}{z}, ymm, ymm, imm8 VGF2P8AFFINEINVQB_YMMu8_MASKmskw_YMMu8_YMMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 CF /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEINVQB ymm {k}{z}, ymm, m256/m64bcst, imm8 VGF2P8AFFINEINVQB_YMMu8_MASKmskw_YMMu8_MEMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 CF /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEINVQB zmm {k}{z}, zmm, zmm, imm8 VGF2P8AFFINEINVQB_ZMMu8_MASKmskw_ZMMu8_ZMMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 CF /r ibAVX10.1 + GFNI or GFNI + AVX512F
VGF2P8AFFINEINVQB zmm {k}{z}, zmm, m512/m64bcst, imm8 VGF2P8AFFINEINVQB_ZMMu8_MASKmskw_ZMMu8_MEMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 CF /r ibAVX10.1 + GFNI or GFNI + AVX512F

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, xmm, xmm, imm8
ymm, ymm, ymm, imm8
xmm {k}{z}, xmm, xmm, imm8no mask
ymm {k}{z}, ymm, ymm, imm8no mask
xmm, xmm, m128, imm8
xmm {k}{z}, xmm, m128/m64bcst, imm8no mask, broadcast
ymm, ymm, m256, imm8
ymm {k}{z}, ymm, m256/m64bcst, imm8no mask, broadcast
xmm {k}{z}, xmm, xmm, imm8with a mask
ymm {k}{z}, ymm, ymm, imm8with a mask
xmm {k}{z}, xmm, xmm, imm8zeroing
ymm {k}{z}, ymm, ymm, imm8zeroing
xmm {k}{z}, xmm, m128/m64bcst, imm8with a mask, zeroingymm {k}{z}, ymm, m256/m64bcst, imm8with a mask, zeroingzmm {k}{z}, zmm, zmm, imm8no maskzmm {k}{z}, zmm, zmm, imm8with a maskzmm {k}{z}, zmm, zmm, imm8zeroingzmm {k}{z}, zmm, m512/m64bcst, imm8no mask, broadcastzmm {k}{z}, zmm, m512/m64bcst, imm8with a mask, zeroing
Ice Lake5 / 0.5p0111 / 0.5p0112 / 0.5p015 / 0.5p015 / 0.5p0111 / 0.5p0112 / 0.5p015 / 0.5p055 / 0.5p055 / 0.5p0512 / 0.5p0512 / 0.5p05
Alder Lake5 / 0.5p0112 / 0.5p0112 / 0.5p01
Sapphire Rapids5 / 0.5p0112 / 0.5p0112 / 0.5p019 / 0.5p0110 / 0.5p0115 / 0.5p0115 / 0.5p015 / 1p09 / 1p010 / 1p012 / 1p015 / 1p0
Lunar Lake4 / 2V0 V110 / 2V0 V111 / 2.33V0 V1
Zen 43 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP33 / 0.5FP0 FP33 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP33 / 1FP0 FP33 / 1FP0 FP33 / 1FP0 FP310 / 1FP0 FP310 / 1FP0 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 within quadwords: each byte of the result comes from the byte in the same place in xmm2 and the quadword around it in xmm3.
VGF2P8AFFINEINVQB: element by elementResult byte i comes from byte i of xmm2 and quadword i/8 of xmm3. Result bytes 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, r1, r0.…01234567xmm2a11111110k1…r0r1r2r3r4r5r7xmm1…0xmm3or m128b

Shown: bytes 7 to 0. Every byte works alike: 16, 32 and 64 bytes in the xmm, ymm and zmm forms. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m64bcst, one quadword from memory stands for every element of the last source.

Result byte i comes from byte i of xmm2 and quadword i/8 of xmm3. Result bytes 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 // 8):
    if k1[i]:                    # 1 without a write mask
        a = src3.q[i // 8]       # the matrix of byte i
        x = gf2p8inv(zmm2.b[i])  # the inverse; 0 for 0
        r = 0
        for j in range(8):       # bit j: row 7 - j
            row = a >> 8 * (7 - j) & 0xFF
            r |= popcount(row & x) % 2 << j
        zmm1.b[i] = r ^ imm8
    elif zeroing:
        zmm1.b[i] = 0
    # else: zmm1.b[i] keeps its value
# m64bcst: src3.q[i] is the m64 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 23 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
VGF2P8AFFINEINVQB xmm, xmm, xmm/m128, imm8 VGF2P8AFFINEINVQB ymm, ymm, ymm/m256, imm8
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
imm8explicitread
VGF2P8AFFINEINVQB xmm {k}{z}, xmm, xmm/m128/m64bcst, imm8 VGF2P8AFFINEINVQB ymm {k}{z}, ymm, ymm/m256/m64bcst, imm8 VGF2P8AFFINEINVQB zmm {k}{z}, zmm, zmm/m512/m64bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread
imm8explicitread

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.

VEX forms
avx-type-4
EVEX forms
AVX512-E4

Attributes

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

EVEX forms
write masking
EVEX memory forms
embedded broadcast (tuple Full)

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VGF2P8AFFINEINVQB, 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_gf2p8affineinv_epi64_epi8 __m128i _mm_gf2p8affineinv_epi64_epi8(__m128i A, __m128i B, const char I)

VGF2P8AFFINEINVQB xmm, xmm, xmm, imm8 VEX.128 -mgfni -mavxwith AVX enabled

_mm_mask_gf2p8affineinv_epi64_epi8 __m128i _mm_mask_gf2p8affineinv_epi64_epi8(__m128i S, __mmask16 U, __m128i A, __m128i B, const char I)

VGF2P8AFFINEINVQB xmm {k}, xmm, xmm, imm8 EVEX.128 -mavx512bw -mavx512vl -mgfni

_mm_maskz_gf2p8affineinv_epi64_epi8 __m128i _mm_maskz_gf2p8affineinv_epi64_epi8(__mmask16 U, __m128i A, __m128i B, const char I)

VGF2P8AFFINEINVQB xmm {k}{z}, xmm, xmm, imm8 EVEX.128 -mavx512bw -mavx512vl -mgfni

_mm256_gf2p8affineinv_epi64_epi8 __m256i _mm256_gf2p8affineinv_epi64_epi8(__m256i A, __m256i B, const char I)

VGF2P8AFFINEINVQB ymm, ymm, ymm, imm8 VEX.256 -mavx -mgfni

_mm256_mask_gf2p8affineinv_epi64_epi8 __m256i _mm256_mask_gf2p8affineinv_epi64_epi8(__m256i S, __mmask32 U, __m256i A, __m256i B, const char I)

VGF2P8AFFINEINVQB ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512bw -mavx512vl -mgfni

_mm256_maskz_gf2p8affineinv_epi64_epi8 __m256i _mm256_maskz_gf2p8affineinv_epi64_epi8(__mmask32 U, __m256i A, __m256i B, const char I)

VGF2P8AFFINEINVQB ymm {k}{z}, ymm, ymm, imm8 EVEX.256 -mavx512bw -mavx512vl -mgfni

_mm512_gf2p8affineinv_epi64_epi8 __m512i _mm512_gf2p8affineinv_epi64_epi8(__m512i A, __m512i B, const char I)

VGF2P8AFFINEINVQB zmm, zmm, zmm, imm8 EVEX.512 -mavx512f -mgfni

_mm512_mask_gf2p8affineinv_epi64_epi8 __m512i _mm512_mask_gf2p8affineinv_epi64_epi8(__m512i S, __mmask64 U, __m512i A, __m512i B, const char I)

VGF2P8AFFINEINVQB zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512bw -mgfni

_mm512_maskz_gf2p8affineinv_epi64_epi8 __m512i _mm512_maskz_gf2p8affineinv_epi64_epi8(__mmask64 U, __m512i A, __m512i B, const char I)

VGF2P8AFFINEINVQB zmm {k}{z}, zmm, zmm, imm8 EVEX.512 -mavx512bw -mgfni

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
AVX_GFNI

GFNI + AVX
CPUID.(EAX=07H,ECX=0):ECX[8] GFNI
CPUID.01H:ECX[28] AVX

Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Zen 4, Zen 5, Zen 6
AVX512_GFNI_128

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

or

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

Ice Lake (client), Tiger Lake, Nova Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512_GFNI_256
Same as AVX512_GFNI_128Same as AVX512_GFNI_128
AVX512_GFNI_512

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

or

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

Same as AVX512_GFNI_128

More GFNI instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-426 (GF2P8AFFINEINVQB)
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  7. 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.