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

VSHUFPD is SHUFPD with a separate destination: in each 128-bit lane, the low double of the result comes from the first source and the high double from the second, each picked by one bit of the immediate, as SHUFPD’s page explains. Unlike VSHUFPS, which applies one immediate to every lane, VSHUFPD gives each lane bits of its own: bits 1:0 for the xmm form, 3:0 for ymm, all eight for zmm, so vshufpd ymm0, ymm1, ymm2, 5 takes the high double of each lane of YMM1 and the low double of each lane of YMM2. Memory needs no alignment, and the destination is zeroed above the vector length. The VEX forms need AVX, ymm included; the EVEX forms (AVX-512F, with AVX512VL below 512 bits, or AVX10.1) add a write mask per double and a broadcast double as the second source. Zen 5’s recorded cases:

  • vshufpd ymm8, ymm15, ymm0, 0x9d gave double 1 of YMM15, double 0 of YMM0, then doubles 3 of each: bits 3:0, 1101b, decided, and bits 7:4 played no part.
  • vshufpd zmm24{k3}, zmm3, qword bcst [mem], 0x65 wrote the double from memory into elements 1, 3, 5 and 7, the odd positions, doubles of ZMM3’s lanes into elements 0 and 6, and kept elements 2 and 4, which k3 leaves clear.

Swaps and fix-ups

In our builds at -O2 with -march=x86-64-v3 and x86-64-v4, the swap _mm_shuffle_pd(a, a, 1) and its ymm twin are VPERMILPD in GCC 14 and VSHUFPD of one register with itself in Clang 23, which also uses vshufpd xmm1, xmm0, xmm0, 1 to bring a high double or a high pair down in horizontal sums. Both compilers swap the real and imaginary parts of a global array of complex doubles with VPERMILPD straight from memory, which VSHUFPD cannot do with one operand in memory. In GCC’s loop at -v3 that builds the complex array from two arrays, VPERMPD spreads the inputs and vshufpd ymm, ymm, ymm, 0xc merges them.

AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows one macro-op on pipes FP0 to FP3, a latency of 1 cycle and four per cycle.

Forms

Every encoding of VSHUFPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSHUFPD xmm, xmm, m128, imm8 VSHUFPD_XMMdq_XMMdq_MEMdq_IMMbVEX.128.66.0F.WIG C6 /r ibAVX
VSHUFPD xmm, xmm, xmm, imm8 VSHUFPD_XMMdq_XMMdq_XMMdq_IMMbVEX.128.66.0F.WIG C6 /r ibAVX
VSHUFPD ymm, ymm, m256, imm8 VSHUFPD_YMMqq_YMMqq_MEMqq_IMMbVEX.256.66.0F.WIG C6 /r ibAVX
VSHUFPD ymm, ymm, ymm, imm8 VSHUFPD_YMMqq_YMMqq_YMMqq_IMMbVEX.256.66.0F.WIG C6 /r ibAVX
VSHUFPD zmm {k}{z}, zmm, zmm, imm8 VSHUFPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_IMM8_AVX512EVEX.512.66.0F.W1 C6 /r ibAVX10.1 or AVX512F
VSHUFPD zmm {k}{z}, zmm, m512/m64bcst, imm8 VSHUFPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_IMM8_AVX512EVEX.512.66.0F.W1 C6 /r ibAVX10.1 or AVX512F
VSHUFPD xmm {k}{z}, xmm, xmm, imm8 VSHUFPD_XMMf64_MASKmskw_XMMf64_XMMf64_IMM8_AVX512EVEX.128.66.0F.W1 C6 /r ibAVX10.1 or AVX512F + AVX512VL
VSHUFPD xmm {k}{z}, xmm, m128/m64bcst, imm8 VSHUFPD_XMMf64_MASKmskw_XMMf64_MEMf64_IMM8_AVX512EVEX.128.66.0F.W1 C6 /r ibAVX10.1 or AVX512F + AVX512VL
VSHUFPD ymm {k}{z}, ymm, ymm, imm8 VSHUFPD_YMMf64_MASKmskw_YMMf64_YMMf64_IMM8_AVX512EVEX.256.66.0F.W1 C6 /r ibAVX10.1 or AVX512F + AVX512VL
VSHUFPD ymm {k}{z}, ymm, m256/m64bcst, imm8 VSHUFPD_YMMf64_MASKmskw_YMMf64_MEMf64_IMM8_AVX512EVEX.256.66.0F.W1 C6 /r ibAVX10.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, imm8
xmm {k}{z}, xmm, m128/m64bcst, imm8
xmm, xmm, xmm, imm8
xmm {k}{z}, xmm, xmm, imm8
ymm {k}{z}, ymm, ymm, imm8
ymm, ymm, m256, imm8
ymm {k}{z}, ymm, m256/m64bcst, imm8
ymm, ymm, ymm, imm8zmm {k}{z}, zmm, zmm, imm8zmm {k}{z}, zmm, m512/m64bcst, imm8
Sandy Bridge, Haswell, Skylake7 / 1p51 / 1p58 / 1p51 / 1p5
Broadwell6 / 1p51 / 1p57 / 1p51 / 1p5
Skylake-SP7 / 1p51 / 1p58 / 1p51 / 1p51 / 1p58 / 1p5
Ice Lake7 / 0.5p151 / 0.5p158 / 0.5p151 / 0.5p151 / 1p58 / 1p5
Alder Lake8 / 0.5p151 / 0.5p159 / 0.5p151 / 0.5p15
Sapphire Rapids8 / 0.5p151 / 0.5p159 / 0.5p151 / 0.5p151 / 1p59 / 1p5
Lunar Lake7 / 2V2 V31 / 0.5V2 V39 / 0.5V2 V31 / 0.5V2 V3
Piledriver7 / 1.5FPFMA FPU0 FPU12 / 1FPFMA FPU0 FPU17 / 2FPFMA FPU0 FPU12 / 2FPFMA FPU0 FPU1
Zen8 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 1FPU1 FPU21 / 1FPU1 FPU2
Zen 28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU2
Zen 38 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP2
Zen 48 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP21 / 1FP1 FP28 / 1FP1 FP2
Jaguar6 / 1FPA FPM FPU0 FPU11 / 0.5FPA FPM FPU0 FPU16 / 2FPA FPM FPU0 FPU11 / 1FPA FPM FPU0 FPU1

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.

Shuffle by immediate: the low double of the result comes from xmm2, the high one from xmm3, each picked by one bit of imm8.
VSHUFPD with imm8 = 0x01With imm8 = 0x01, result doubles 1 to 0: b0, a1.10imm80x0101xmm2a11k1a1b0xmm101xmm3or m128b

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

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

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 // 64):
    j = i - i % 2 + (imm8 >> i & 1)
    if k1[i]:  # 1 without a write mask
        if i % 2 == 0:
            zmm1.q[i] = zmm2.q[j]
        else:
            zmm1.q[i] = src3.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.

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
VSHUFPD xmm, xmm, xmm/m128, imm8 VSHUFPD ymm, ymm, ymm/m256, imm8
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
imm8explicitread
VSHUFPD xmm {k}{z}, xmm, xmm/m128/m64bcst, imm8 VSHUFPD ymm {k}{z}, ymm, ymm/m256/m64bcst, imm8 VSHUFPD 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-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 VSHUFPD, 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
_mm256_shuffle_pd __m256d _mm256_shuffle_pd(__m256d a, __m256d b, const int mask)

VSHUFPD ymm, ymm, ymm, imm8 VEX.256 -mavx

_mm256_mask_permute_pd __m256d _mm256_mask_permute_pd(__m256d W, __mmask8 U, __m256d X, const int C)

VSHUFPD ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_mask_shuffle_pd __m256d _mm256_mask_shuffle_pd(__m256d W, __mmask8 U, __m256d A, __m256d B, const int M)

VSHUFPD ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_maskz_permute_pd __m256d _mm256_maskz_permute_pd(__mmask8 U, __m256d X, const int C)

VSHUFPD ymm {k}{z}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm256_maskz_shuffle_pd __m256d _mm256_maskz_shuffle_pd(__mmask8 U, __m256d A, __m256d B, const int M)

VSHUFPD ymm {k}{z}, ymm, ymm, imm8 EVEX.256 -mavx512vl

_mm512_permute_pd __m512d _mm512_permute_pd(__m512d X, const int C)

VSHUFPD zmm, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_shuffle_pd __m512d _mm512_shuffle_pd(__m512d A, __m512d B, const int M)

VSHUFPD zmm, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_mask_permute_pd __m512d _mm512_mask_permute_pd(__m512d W, __mmask8 U, __m512d X, const int C)

VSHUFPD zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_mask_shuffle_pd __m512d _mm512_mask_shuffle_pd(__m512d W, __mmask8 U, __m512d A, __m512d B, const int M)

VSHUFPD zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_maskz_permute_pd __m512d _mm512_maskz_permute_pd(__mmask8 U, __m512d X, const int C)

VSHUFPD zmm {k}{z}, zmm, zmm, imm8 EVEX.512 -mavx512f

_mm512_maskz_shuffle_pd __m512d _mm512_maskz_shuffle_pd(__mmask8 U, __m512d A, __m512d B, const int M)

VSHUFPD zmm {k}{z}, zmm, zmm, imm8 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 2B, page 4-646 (SHUFPD)
  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.