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

VGF2P8AFFINEQB multiplies every byte by an 8-by-8 bit matrix and XORs in the immediate: the VEX and EVEX forms of GF2P8AFFINEQB, whose page covers how the matrix is read and what compilers build from it. The VEX forms need GFNI and AVX, at both widths; the EVEX forms need GFNI with AVX512F, plus AVX512VL below 512 bits, or AVX10.1. All take a separate destination and memory at any alignment, and clear the register above the vector length. EVEX adds a write mask per byte and a matrix broadcast from one quadword of memory, the usual case of one transform for every byte.

A matrix per quadword

The matrix stays a quadword of the second source for the 8 bytes in the same position, so a wide register can hold a different one for each quadword. On Zen 5, the recorded vgf2p8affineqb ymm8, ymm15, ymm0, 0x80 used the identity in the first quadword, the bit reversal in the second and all ones in the third, which puts the parity of each byte into all eight bits: after the XOR with 80h, 5Fh, with six bits set, became 80h and 89h, with three, 7Fh. vgf2p8affineqb ymm17{k4}, ymm30, qword bcst [mem], 0xff broadcast the all-ones matrix and wrote only the bytes k4 selects: 53h became FFh in byte 3, while byte 2, its mask bit clear, kept 49h.

In compiled code

GFNI is in neither x86-64-v3 nor v4, so our builds at -O2 add -mgfni. Clang 23 then compiles the byte shifts and rotates by a constant and the bit reversal loop over fixed-size uint8_t arrays to one VPBROADCASTQ of the matrix and one VGF2P8AFFINEQB per 32 bytes, on ymm registers at both levels. GCC 14 emits it only for the intrinsics, shifting words and masking for the shifts. For _mm512_gf2p8affine_epi64_epi8 with a matrix from _mm512_set1_epi64, Clang reads it as a broadcast quadword, while GCC loads a full 64-byte constant.

AMD’s latency spreadsheet for Zen 5 gives the VEX row and the EVEX row the legacy form’s figures: one macro-op, a latency of 3 cycles and two per cycle.

Forms

Every encoding of VGF2P8AFFINEQB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VGF2P8AFFINEQB xmm, xmm, xmm, imm8 VGF2P8AFFINEQB_XMMu8_XMMu8_XMMu64_IMM8VEX.128.66.0F3A.W1 CE /r ibGFNI + AVX
VGF2P8AFFINEQB xmm, xmm, m128, imm8 VGF2P8AFFINEQB_XMMu8_XMMu8_MEMu64_IMM8VEX.128.66.0F3A.W1 CE /r ibGFNI + AVX
VGF2P8AFFINEQB ymm, ymm, ymm, imm8 VGF2P8AFFINEQB_YMMu8_YMMu8_YMMu64_IMM8VEX.256.66.0F3A.W1 CE /r ibGFNI + AVX
VGF2P8AFFINEQB ymm, ymm, m256, imm8 VGF2P8AFFINEQB_YMMu8_YMMu8_MEMu64_IMM8VEX.256.66.0F3A.W1 CE /r ibGFNI + AVX
VGF2P8AFFINEQB xmm {k}{z}, xmm, xmm, imm8 VGF2P8AFFINEQB_XMMu8_MASKmskw_XMMu8_XMMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 CE /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEQB xmm {k}{z}, xmm, m128/m64bcst, imm8 VGF2P8AFFINEQB_XMMu8_MASKmskw_XMMu8_MEMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 CE /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEQB ymm {k}{z}, ymm, ymm, imm8 VGF2P8AFFINEQB_YMMu8_MASKmskw_YMMu8_YMMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 CE /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEQB ymm {k}{z}, ymm, m256/m64bcst, imm8 VGF2P8AFFINEQB_YMMu8_MASKmskw_YMMu8_MEMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 CE /r ibAVX10.1 + GFNI or GFNI + AVX512F + AVX512VL
VGF2P8AFFINEQB zmm {k}{z}, zmm, zmm, imm8 VGF2P8AFFINEQB_ZMMu8_MASKmskw_ZMMu8_ZMMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 CE /r ibAVX10.1 + GFNI or GFNI + AVX512F
VGF2P8AFFINEQB zmm {k}{z}, zmm, m512/m64bcst, imm8 VGF2P8AFFINEQB_ZMMu8_MASKmskw_ZMMu8_MEMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 CE /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.
VGF2P8AFFINEQB: 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 = zmm2.b[i]
        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
VGF2P8AFFINEQB xmm, xmm, xmm/m128, imm8 VGF2P8AFFINEQB ymm, ymm, ymm/m256, imm8
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
imm8explicitread
VGF2P8AFFINEQB xmm {k}{z}, xmm, xmm/m128/m64bcst, imm8 VGF2P8AFFINEQB ymm {k}{z}, ymm, ymm/m256/m64bcst, imm8 VGF2P8AFFINEQB 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 VGF2P8AFFINEQB, 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_gf2p8affine_epi64_epi8 __m128i _mm_gf2p8affine_epi64_epi8(__m128i A, __m128i B, const char I)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

VGF2P8AFFINEQB 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-429 (GF2P8AFFINEQB)
  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.