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

VPERMI2D looks up doublewords in a table of two registers. The destination starts out holding the indices; the two sources are the table, the first source its low half and the second its high half. For each element, the low bits of the index choose an element and the next bit chooses the register: with 16 doublewords per ZMM register, bits 3:0 choose the element and bit 4 the source, so the indices 0 to 31 cover all 32 doublewords of the two. Higher bits are ignored. In XMM and YMM registers the table holds 8 or 16 elements and the index bits shrink to match.

The results overwrite the indices, which is the I in the name. VPERMT2D computes the same selection with the indices in a source and the result over the first table instead (T for table). The intrinsic _mm512_permutex2var_epi32(a, idx, b) stands for both, and the compiler picks whichever overwrites a register it no longer needs: GCC 14 and Clang 23 at -O2 with -mavx512f compile it to VPERMI2D when only the index is free and to VPERMT2D when the first table is. The two differ where a merge mask leaves elements alone: there VPERMI2D keeps the index and VPERMT2D the first table’s element. So the merge-masked intrinsics are two: _mm512_mask2_permutex2var_epi32, with the mask after idx, falls back to the index and is VPERMI2D, and _mm512_mask_permutex2var_epi32, with the mask after a, falls back to a and is VPERMT2D.

Uses

  • Splitting interleaved data. Two index vectors of the even and the odd positions, 0, 2, 4 … 30 and 1, 3, 5 … 31, separate the real and imaginary parts of 16 complex numbers loaded in two registers. Intel’s optimization manual does this with VPERMI2D and VPERMT2D in place of a gather (Section 17.22.1, Example 17-31); both compilers vectorize such a loop with VPERMT2D, and Clang with VPERMI2D where the index register is no longer needed.
  • Small tables. A table of 32 entries fits in two registers, so a lookup that would otherwise be a gather is one instruction; Intel’s manual reports large gains in exp, log and pow from such lookups (Section 17.15.7).

VPERMI2Q, VPERMI2PS and VPERMI2W do the same for other elements, and VPERMI2B for bytes, with AVX512_VBMI. For one register of table, VPERMD is enough.

In the optimization guide

What the optimization guide says about VPERMI2D, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Vectors

  • Shuffles and lane crossing: AVX-512’s two-source permutes and VBMI’s VPERMB take any element of their sources, each in one macro-op on Zen 5.

Forms

Every encoding of VPERMI2D that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPERMI2D zmm {k}{z}, zmm, zmm VPERMI2D_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512EVEX.512.66.0F38.W0 76 /rAVX10.1 or AVX512F
VPERMI2D zmm {k}{z}, zmm, m512/m32bcst VPERMI2D_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512EVEX.512.66.0F38.W0 76 /rAVX10.1 or AVX512F
VPERMI2D xmm {k}{z}, xmm, xmm VPERMI2D_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512EVEX.128.66.0F38.W0 76 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2D xmm {k}{z}, xmm, m128/m32bcst VPERMI2D_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512EVEX.128.66.0F38.W0 76 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2D ymm {k}{z}, ymm, ymm VPERMI2D_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512EVEX.256.66.0F38.W0 76 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2D ymm {k}{z}, ymm, m256/m32bcst VPERMI2D_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512EVEX.256.66.0F38.W0 76 /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}, zmm, zmmzmm {k}{z}, zmm, m512/m32bcst
ymm {k}{z}, ymm, m256/m32bcst
xmm {k}{z}, xmm, xmmxmm {k}{z}, xmm, m128/m32bcstymm {k}{z}, ymm, ymm
Skylake-SP, Ice Lake3 / 1p510 / 1p53 / 1p59 / 1p53 / 1p5
Sapphire Rapids3 / 1p511 / 1p53 / 1p510 / 1p53 / 1p5
Zen 45 / 1FP1 FP28 / 0.5FP1 FP23 / 11FP1 FP28 / 0.5FP1 FP24 / 12FP1 FP2
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2232; AMD 58455, row 585).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2233; AMD 58455, row 586).

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.

Permute from two tables: each doubleword of the result is the doubleword that the index in the same place of zmm1 numbers in zmm2 or, with the index's next bit set, in zmm3.
VPERMI2D with an example index vectorWith the example indices, result doublewords 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, a10, a1, b5, b12, a5, a15, b2, a9, b6, b14, a0, b1, a3.317030229181552821110231324zmm1index0135910131524678111214zmm2a1111111111111110k1a3a0a9a15a5a1a10b1b14b6b2b12b5b7b8zmm10349101113151256781214zmm3or m512b

Example index vector in zmm1 (element 0 on the right); only its low 5 bits count. Shown for the zmm form; the xmm and ymm forms work the same on 4 and 8 doublewords. Under the mask, a masked-off element keeps the old value of zmm1, the index.

With the example indices, result doublewords 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, a10, a1, b5, b12, a5, a15, b2, a9, b6, b14, a0, b1, a3.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

n = VL // 32           # 4 in xmm, 8 in ymm, 16 in zmm
for i in range(n):
    if k1[i]:
        x = zmm1.d[i]  # the index, in zmm1
        if x & n:
            zmm1.d[i] = src3.d[x % n]
        else:
            zmm1.d[i] = zmm2.d[x % n]
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 6 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
VPERMI2D xmm {k}{z}, xmm, xmm/m128/m32bcst VPERMI2D ymm {k}{z}, ymm, ymm/m256/m32bcst VPERMI2D zmm {k}{z}, zmm, zmm/m512/m32bcst
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
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-E4NF

Attributes

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

All forms
write masking
Memory forms
embedded broadcast (tuple Full)

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPERMI2D, 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_permutex2var_epi32 __m128i _mm_permutex2var_epi32(__m128i __A, __m128i __I, __m128i __B)

VPERMI2D xmm, xmm, xmm EVEX.128 -mavx512vlwhen __I is already in the destination register

_mm_mask2_permutex2var_epi32 __m128i _mm_mask2_permutex2var_epi32(__m128i __A, __m128i __I, __mmask8 __U, __m128i __B)

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

_mm_maskz_permutex2var_epi32 __m128i _mm_maskz_permutex2var_epi32(__mmask8 __U, __m128i __A, __m128i __I, __m128i __B)

VPERMI2D xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vlwhen __I is already in the destination register

_mm256_permutex2var_epi32 __m256i _mm256_permutex2var_epi32(__m256i __A, __m256i __I, __m256i __B)

VPERMI2D ymm, ymm, ymm EVEX.256 -mavx512vlwhen __I is already in the destination register

_mm256_mask2_permutex2var_epi32 __m256i _mm256_mask2_permutex2var_epi32(__m256i __A, __m256i __I, __mmask8 __U, __m256i __B)

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

_mm256_maskz_permutex2var_epi32 __m256i _mm256_maskz_permutex2var_epi32(__mmask8 __U, __m256i __A, __m256i __I, __m256i __B)

VPERMI2D ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vlwhen __I is already in the destination register

_mm512_permutex2var_epi32 __m512i _mm512_permutex2var_epi32(__m512i __A, __m512i __I, __m512i __B)

VPERMI2D zmm, zmm, zmm EVEX.512 -mavx512fwhen __I is already in the destination register

_mm512_mask2_permutex2var_epi32 __m512i _mm512_mask2_permutex2var_epi32(__m512i __A, __m512i __I, __mmask16 __U, __m512i __B)

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

_mm512_maskz_permutex2var_epi32 __m512i _mm512_maskz_permutex2var_epi32(__mmask16 __U, __m512i __A, __m512i __I, __m512i __B)

VPERMI2D zmm {k}{z}, zmm, zmm EVEX.512 -mavx512fwhen __I is already in the destination register

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-505 (VPERMI2W/D/Q/PS/PD)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)

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.