Extensions
Forms
20 (8 VEX, 12 EVEX)
Data
Intel XED v2026.08.23

VPERMILPD chooses, for each double of the result, one of the two doubles of the same 128-bit lane of its source. It is the double-precision side of VPERMILPS, whose page covers the two kinds of control and the rule that no element leaves its lane; VPERMPD crosses lanes. With only two candidates per lane, each element needs one selector bit, and the two controls place it differently from the single-precision form.

Bit 1 of each quadword

In the vector form, the bit that chooses is bit 1 of the matching quadword of the control; bit 0 and the other 62 bits are ignored. Zen 5’s recorded case vpermilpd ymm7, ymm11, ymm7 shows it with control quadwords ending in 2Ch, 36h, F2h and 99h: the first and the last, with bit 1 clear, took the low double of their lane, although 99h has bit 0 set; the other two took the high one. A control vector of indices 0 and 1, as VPERMILPS would read them, therefore selects the low double everywhere; indices must be doubled, 0 and 2.

One immediate bit per element

The immediate form gives each element its own bit, not one pattern repeated per lane: bits 1:0 for an xmm register, 3:0 for ymm and all eight for zmm. vpermilpd ymm4, ymm4, 0x57 (bits 3:0 are 0111b) took element 1 into elements 0 and 1, element 3 into element 2 and element 2 into element 3, on Zen 5 as in the manuals. Swapping the two doubles of every lane is 1 for xmm and 5 for ymm.

In compiled code

GCC 14 at -O2 with -mavx emits the immediate form for one-register shuffles of doubles within lanes: vpermilpd xmm0, xmm0, 1 for a swap, 5 for the swap in both lanes of a ymm register and 0 to repeat the low double of each lane. Clang 23 writes the swaps as VSHUFPD of a register with itself and the repeat as VMOVDDUP, and uses VPERMILPD when the source comes from memory, as with VPERMILPS. Both emit the vector form for _mm256_permutevar_pd. AMD’s Zen 5 guide gives the immediate form a latency of 1 cycle on all four vector pipes and the vector form 2 cycles on two.

Forms

Every encoding of VPERMILPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPERMILPD xmm, xmm, m128 VPERMILPD_XMMdq_XMMdq_MEMdqVEX.128.66.0F38.W0 0D /rAVX
VPERMILPD xmm, xmm, xmm VPERMILPD_XMMdq_XMMdq_XMMdqVEX.128.66.0F38.W0 0D /rAVX
VPERMILPD ymm, ymm, m256 VPERMILPD_YMMqq_YMMqq_MEMqqVEX.256.66.0F38.W0 0D /rAVX
VPERMILPD ymm, ymm, ymm VPERMILPD_YMMqq_YMMqq_YMMqqVEX.256.66.0F38.W0 0D /rAVX
VPERMILPD xmm, m128, imm8 VPERMILPD_XMMdq_MEMdq_IMMbVEX.128.66.0F3A.W0 05 /r ibAVX
VPERMILPD xmm, xmm, imm8 VPERMILPD_XMMdq_XMMdq_IMMbVEX.128.66.0F3A.W0 05 /r ibAVX
VPERMILPD ymm, m256, imm8 VPERMILPD_YMMqq_MEMqq_IMMbVEX.256.66.0F3A.W0 05 /r ibAVX
VPERMILPD ymm, ymm, imm8 VPERMILPD_YMMqq_YMMqq_IMMbVEX.256.66.0F3A.W0 05 /r ibAVX
VPERMILPD zmm {k}{z}, zmm, imm8 VPERMILPD_ZMMf64_MASKmskw_ZMMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 05 /r ibAVX10.1 or AVX512F
VPERMILPD zmm {k}{z}, m512/m64bcst, imm8 VPERMILPD_ZMMf64_MASKmskw_MEMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 05 /r ibAVX10.1 or AVX512F
VPERMILPD zmm {k}{z}, zmm, zmm VPERMILPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F38.W1 0D /rAVX10.1 or AVX512F
VPERMILPD zmm {k}{z}, zmm, m512/m64bcst VPERMILPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F38.W1 0D /rAVX10.1 or AVX512F
VPERMILPD xmm {k}{z}, xmm, imm8 VPERMILPD_XMMf64_MASKmskw_XMMf64_IMM8_AVX512EVEX.128.66.0F3A.W1 05 /r ibAVX10.1 or AVX512F + AVX512VL
VPERMILPD xmm {k}{z}, m128/m64bcst, imm8 VPERMILPD_XMMf64_MASKmskw_MEMf64_IMM8_AVX512EVEX.128.66.0F3A.W1 05 /r ibAVX10.1 or AVX512F + AVX512VL
VPERMILPD xmm {k}{z}, xmm, xmm VPERMILPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F38.W1 0D /rAVX10.1 or AVX512F + AVX512VL
VPERMILPD xmm {k}{z}, xmm, m128/m64bcst VPERMILPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F38.W1 0D /rAVX10.1 or AVX512F + AVX512VL
VPERMILPD ymm {k}{z}, ymm, imm8 VPERMILPD_YMMf64_MASKmskw_YMMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 05 /r ibAVX10.1 or AVX512F + AVX512VL
VPERMILPD ymm {k}{z}, m256/m64bcst, imm8 VPERMILPD_YMMf64_MASKmskw_MEMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 05 /r ibAVX10.1 or AVX512F + AVX512VL
VPERMILPD ymm {k}{z}, ymm, ymm VPERMILPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F38.W1 0D /rAVX10.1 or AVX512F + AVX512VL
VPERMILPD ymm {k}{z}, ymm, m256/m64bcst VPERMILPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F38.W1 0D /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.
Modelxmm, xmm, m128
xmm {k}{z}, xmm, m128/m64bcst
xmm, xmm, xmmymm, ymm, m256
ymm {k}{z}, ymm, m256/m64bcst
ymm, ymm, ymm
zmm {k}{z}, zmm, zmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm, m128, imm8
xmm {k}{z}, m128/m64bcst, imm8
xmm, xmm, imm8
xmm {k}{z}, xmm, imm8
ymm {k}{z}, ymm, imm8
ymm, m256, imm8
ymm {k}{z}, m256/m64bcst, imm8
ymm, ymm, imm8zmm {k}{z}, zmm, imm8zmm {k}{z}, m512/m64bcst, imm8zmm {k}{z}, zmm, m512/m64bcst
Sandy Bridge, Haswell, Skylake7 / 1p51 / 1p58 / 1p51 / 1p57 / 1p51 / 1p58 / 1p51 / 1p5
Broadwell6 / 1p51 / 1p57 / 1p51 / 1p56 / 1p51 / 1p57 / 1p51 / 1p5
Skylake-SP, Ice Lake7 / 1p51 / 1p58 / 1p51 / 1p57 / 1p51 / 1p58 / 1p51 / 1p51 / 1p58 / 1p58 / 1p5
Alder Lake8 / 1p51 / 1p59 / 1p51 / 1p58 / 1p51 / 1p59 / 1p51 / 1p5
Sapphire Rapids8 / 1p51 / 1p59 / 1p51 / 1p58 / 1p51 / 1p59 / 1p51 / 1p51 / 1p59 / 1p59 / 1p5
Lunar Lake8 / 0.5V2 V31 / 0.5V2 V39 / 0.5V2 V31 / 0.5V2 V37 / 2V2 V31 / 0.5V2 V39 / 0.5V2 V31 / 0.5V2 V3
Piledriver8 / 1.5FPU1 FPXBR3 / 1FPU1 FPXBR8 / 2FPU1 FPXBR3 / 2FPU1 FPXBR7 / 1.5FPFMA FPU0 FPU12 / 1FPFMA FPU0 FPU17 / 2FPFMA FPU0 FPU12 / 2FPFMA FPU0 FPU1
Zen8 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 1FPU1 FPU21 / 1FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 1FPU1 FPU21 / 1FPU1 FPU2
Zen 210 / 0.5FPU1 FPU23 / 0.5FPU1 FPU210 / 0.5FPU1 FPU23 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU2
Zen 310 / 0.5FP1 FP23 / 0.5FP1 FP210 / 0.5FP1 FP23 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP2
Zen 410 / 0.5FP1 FP23 / 0.5FP1 FP210 / 0.5FP1 FP22 / 0.671FP1 FP2 FP38 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP21 / 1FP1 FP28 / 1FP1 FP210 / 1FP1 FP2
Jaguar8 / 2FPA FPM FPU0 FPU13 / 2FPA FPM FPU0 FPU19 / 3FPA FPM FPU0 FPU14 / 3FPA FPM FPU0 FPU16 / 1FPA FPM FPU0 FPU11 / 0.5FPA FPM FPU0 FPU16 / 2FPA FPM FPU0 FPU11 / 1FPA FPM FPU0 FPU1
  1. Zen 4 model, ymm form: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2259; AMD 58455, row 1324).

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 within lanes by index: each double of the result is the double of its lane of xmm2 that the index in the same place numbers, in bit 1 of the index.VPERMILPD xmm, xmm, xmm/m128 VPERMILPD ymm, ymm, ymm/m256 VPERMILPD xmm {k}{z}, xmm, xmm/m128/m64bcst VPERMILPD ymm {k}{z}, ymm, ymm/m256/m64bcst VPERMILPD zmm {k}{z}, zmm, zmm/m512/m64bcst
VPERMILPD with an example index vectorWith the example indices, result doubles 1 to 0: a0, a1.01xmm2a11k1a1a0xmm120xmm3or m128

Example index vector in xmm3 (element 0 on the right); only bit 1 counts. The ymm and zmm forms repeat this in each 128-bit lane. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

With the example indices, result doubles 1 to 0: a0, a1.

Shuffle by immediate: one bit of imm8 per result double picks one of the two doubles of the lane.VPERMILPD xmm, xmm/m128, imm8 VPERMILPD ymm, ymm/m256, imm8 VPERMILPD xmm {k}{z}, xmm/m128/m64bcst, imm8 VPERMILPD ymm {k}{z}, ymm/m256/m64bcst, imm8 VPERMILPD zmm {k}{z}, zmm/m512/m64bcst, imm8
VPERMILPD with imm8 = 0x01With imm8 = 0x01, result doubles 1 to 0: a0, a1.xmm2or m128a10imm80x01

Example: imm8 = 0x01 (0000 0001 in binary). The ymm and zmm forms repeat this in each 128-bit lane, with the next bits of imm8. 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 double from memory stands for every element of xmm2.

With imm8 = 0x01, result doubles 1 to 0: a0, a1.

Operation

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

VPERMILPD xmm, xmm, xmm/m128 VPERMILPD ymm, ymm, ymm/m256 VPERMILPD xmm {k}{z}, xmm, xmm/m128/m64bcst VPERMILPD ymm {k}{z}, ymm, ymm/m256/m64bcst VPERMILPD zmm {k}{z}, zmm, zmm/m512/m64bcst
for i in range(VL // 64):
    if k1[i]:  # 1 without a write mask
        x = src3.q[i]
        j = i - i % 2 + (x >> 1 & 1)
        zmm1.q[i] = zmm2.q[j]
    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): 10 cases.

VPERMILPD xmm, xmm/m128, imm8 VPERMILPD ymm, ymm/m256, imm8 VPERMILPD xmm {k}{z}, xmm/m128/m64bcst, imm8 VPERMILPD ymm {k}{z}, ymm/m256/m64bcst, imm8 VPERMILPD zmm {k}{z}, zmm/m512/m64bcst, imm8
for i in range(VL // 64):
    j = i - i % 2 + (imm8 >> i & 1)
    if k1[i]:  # 1 without a write mask
        zmm1.q[i] = src2.q[j]
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src2.f64[i] is the m64 for every i
# zmm1 is zeroed from bit VL up

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

VEX forms
avx-type-6
EVEX forms
AVX512-E4NF

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 VPERMILPD, 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_permutevar_pd __m128d _mm_permutevar_pd(__m128d __a, __m128i __c)

VPERMILPD xmm, xmm, xmm VEX.128 -mavx

_mm_mask_permutevar_pd __m128d _mm_mask_permutevar_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128i __C)

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

_mm_maskz_permutevar_pd __m128d _mm_maskz_permutevar_pd(__mmask8 __U, __m128d __A, __m128i __C)

VPERMILPD xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl

_mm256_permute_pd __m256d _mm256_permute_pd(__m256d A, const int C)

VPERMILPD ymm, m256, imm8 VEX.256 -mavxwhen A comes from memory

_mm256_permutevar_pd __m256d _mm256_permutevar_pd(__m256d __a, __m256i __c)

VPERMILPD ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_permutevar_pd __m256d _mm256_mask_permutevar_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256i __C)

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

_mm256_maskz_permutevar_pd __m256d _mm256_maskz_permutevar_pd(__mmask8 __U, __m256d __A, __m256i __C)

VPERMILPD ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm512_permutevar_pd __m512d _mm512_permutevar_pd(__m512d __A, __m512i __C)

VPERMILPD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_permutevar_pd __m512d _mm512_mask_permutevar_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512i __C)

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

_mm512_maskz_permutevar_pd __m512d _mm512_maskz_permutevar_pd(__mmask8 __U, __m512d __A, __m512i __C)

VPERMILPD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

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

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
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 AVX instructions

All 253 AVX 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 2C, page 5-511 (VPERMILPD)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. 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.