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

VPERMI2PD picks doubles from a table of two registers, with the indices in the destination, which the results then overwrite. It is the I form of VPERMT2PD, which overwrites the first table instead, and VPERMI2D explains the pair. Per quadword index, bits 2:0 pick the element and bit 3 the table at 512 bits, one bit fewer for each halving of the width. The doubles move as bit patterns, so MXCSR plays no part.

Recorded on Zen 5

  • The index register is a table too. In vpermi2pd zmm7{k6}, zmm12, zmm7, ZMM7 held the indices and the second table: element 2’s index ended in 1011b and took ZMM7’s own old element 3, element 5’s ended in 0011b and took element 3 of ZMM12. The elements K6 left out kept their indices.
  • Merging keeps the indices. In vpermi2pd zmm1{k7}, zmm2, qword bcst [mem], elements 2 to 4, left out by E3h, kept their index values, where a merging VPERMT2PD keeps the table; elements 1 and 5 to 7 had bit 3 set and took the broadcast double.
  • Two bits at 128 bits. {evex} vpermi2pd xmm5, xmm5, xmm5 read indices ending in 1101b and 0101b; with bit 1 clear in both, both took element 1 of XMM5.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 emit VPERMI2PD for _mm512_mask2_permutex2var_pd, whose unselected elements keep the index, and when the first table is still needed afterwards, as in _mm512_permutex2var_pd(a, idx, b) added to a. For a fixed shuffle of two vectors with __builtin_shufflevector, the odd elements or the interleave 0, 8, 1, 9 …, GCC loads the indices into the destination and uses VPERMI2PD, while Clang uses VPERMT2PD.

AMD’s Zen 5 latency spreadsheet gives VPERMI2PD 3, 4 and 5 cycles for XMM, YMM and ZMM registers, two per cycle on pipes FP1 and FP2.

Forms

Every encoding of VPERMI2PD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPERMI2PD zmm {k}{z}, zmm, zmm VPERMI2PD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F38.W1 77 /rAVX10.1 or AVX512F
VPERMI2PD zmm {k}{z}, zmm, m512/m64bcst VPERMI2PD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F38.W1 77 /rAVX10.1 or AVX512F
VPERMI2PD xmm {k}{z}, xmm, xmm VPERMI2PD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F38.W1 77 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2PD xmm {k}{z}, xmm, m128/m64bcst VPERMI2PD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F38.W1 77 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2PD ymm {k}{z}, ymm, ymm VPERMI2PD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F38.W1 77 /rAVX10.1 or AVX512F + AVX512VL
VPERMI2PD ymm {k}{z}, ymm, m256/m64bcst VPERMI2PD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F38.W1 77 /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/m64bcst
ymm {k}{z}, ymm, m256/m64bcst
xmm {k}{z}, xmm, xmmxmm {k}{z}, xmm, m128/m64bcstymm {k}{z}, ymm, ymm
Skylake-SP, Ice Lake3 / 1p510 / 1p53 / 1p59 / 1p53 / 1p5
Sapphire Rapids3 / 1p511 / 1p53 / 1p510 / 1p53 / 1p5
Zen 45 / 1FP1 FP214 / 1FP13 / 11FP1 FP214 / 1FP14 / 12FP1 FP2
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2235; AMD 58455, row 594).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2236; AMD 58455, row 595).

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 double of the result is the double that the index in the same place of zmm1 numbers in zmm2 or, with the index's next bit set, in zmm3.
VPERMI2PD with an example index vectorWith the example indices, result doubles 7 to 0: b7, unchanged (bit 6 of k1 is 0), b1, a6, b6, a0, a1, a3.3170302291815zmm1index01236457zmm2a11111110k1a3a1a0a6b6b1b7zmm102345167zmm3or m512b

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

With the example indices, result doubles 7 to 0: b7, unchanged (bit 6 of k1 is 0), b1, a6, b6, a0, a1, a3.

Operation

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

n = VL // 64           # 2 in xmm, 4 in ymm, 8 in zmm
for i in range(n):
    if k1[i]:
        x = zmm1.q[i]  # the index, in zmm1
        if x & n:
            zmm1.q[i] = src3.q[x % n]
        else:
            zmm1.q[i] = zmm2.q[x % n]
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src3.f64[i] is the m64 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
VPERMI2PD xmm {k}{z}, xmm, xmm/m128/m64bcst VPERMI2PD ymm {k}{z}, ymm, ymm/m256/m64bcst VPERMI2PD zmm {k}{z}, zmm, zmm/m512/m64bcst
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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 VPERMI2PD, 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_pd __m128d _mm_permutex2var_pd(__m128d __A, __m128i __I, __m128d __B)

VPERMI2PD xmm, xmm, xmm EVEX.128 -mavx512vlwhen __A comes from memory

_mm_mask2_permutex2var_pd __m128d _mm_mask2_permutex2var_pd(__m128d __A, __m128i __I, __mmask8 __U, __m128d __B)

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

_mm_maskz_permutex2var_pd __m128d _mm_maskz_permutex2var_pd(__mmask8 __U, __m128d __A, __m128i __I, __m128d __B)

VPERMI2PD xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vlwhen __A comes from memory

_mm256_permutex2var_pd __m256d _mm256_permutex2var_pd(__m256d __A, __m256i __I, __m256d __B)

VPERMI2PD ymm, ymm, ymm EVEX.256 -mavx512vlwhen __A comes from memory

_mm256_mask2_permutex2var_pd __m256d _mm256_mask2_permutex2var_pd(__m256d __A, __m256i __I, __mmask8 __U, __m256d __B)

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

_mm256_maskz_permutex2var_pd __m256d _mm256_maskz_permutex2var_pd(__mmask8 __U, __m256d __A, __m256i __I, __m256d __B)

VPERMI2PD ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vlwhen __A comes from memory

_mm512_permutex2var_pd __m512d _mm512_permutex2var_pd(__m512d __A, __m512i __I, __m512d __B)

VPERMI2PD zmm, zmm, zmm EVEX.512 -mavx512fwhen __A comes from memory

_mm512_mask2_permutex2var_pd __m512d _mm512_mask2_permutex2var_pd(__m512d __A, __m512i __I, __mmask8 __U, __m512d __B)

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

_mm512_maskz_permutex2var_pd __m512d _mm512_maskz_permutex2var_pd(__mmask8 __U, __m512d __A, __m512i __I, __m512d __B)

VPERMI2PD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512fwhen __A comes from memory

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. 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.