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

VSHUFF64X2 builds a ZMM or YMM register from 128-bit blocks of two sources, each block chosen by a field of the immediate, and writes the result under a mask of doubles. It is VSHUFI64X2 under a floating-point name, and that page explains the immediate, the 256-bit form and what a mask of quadwords can do with half-blocks; VSHUFF32X4 moves the same blocks under a mask of singles. It moves bits without arithmetic, so MXCSR is left alone.

Recorded on Zen 5

  • Two sources. vshuff64x2 zmm17{k3}, zmm30, zmm2, 0x96 built blocks 2 and 1 of ZMM30 and blocks 1 and 2 of ZMM2, and with EBh in K3 wrote doubles 0, 1, 3, 5, 6 and 7, keeping 2 and 4.
  • Broadcast. vshuff64x2 zmm9{k1}, zmm9, qword bcst [mem], 0xec wrote the one memory double to elements 5 and 7, the bits K1 (A0h) selects.
  • 256 bits, zeroing. vshuff64x2 ymm0{k3}{z}, ymm31, ymm16, 0x5f read only bits 1:0 of 5Fh, took the high block of each source, and zeroed double 2, whose mask bit is clear.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 compile _mm512_shuffle_f64x2 to VSHUFF64X2, and also __builtin_shufflevector on vectors of eight doubles when it moves whole blocks: reversing them (0x1b), repeating one or joining the high halves of two vectors (0xee). Both repeat one XMM register four times, _mm512_broadcast_f64x2, with vshuff64x2 zmm0, zmm0, zmm0, 0. Clang uses VSHUFF64X2 for the unmasked _mm512_shuffle_f32x4 and _mm512_broadcast_f32x4 as well, where GCC keeps VSHUFF32X4. To repeat a YMM register twice, _mm512_broadcast_f64x4, GCC uses VSHUFF64X2 with 0x44 and Clang VINSERTF64X4, and at 256 bits Clang compiles _mm256_shuffle_f64x2 to the VEX VPERM2F128.

AMD’s Zen 5 latency spreadsheet gives VSHUFF64X2 one macro-op on pipe FP1 or FP2, 3 cycles at 256 bits and 5 at 512, two per cycle, as VSHUFI64X2.

Forms

Every encoding of VSHUFF64X2 that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSHUFF64X2 zmm {k}{z}, zmm, zmm, imm8 VSHUFF64X2_ZMMf64_MASKmskw_ZMMf64_ZMMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 23 /r ibAVX10.1 or AVX512F
VSHUFF64X2 zmm {k}{z}, zmm, m512/m64bcst, imm8 VSHUFF64X2_ZMMf64_MASKmskw_ZMMf64_MEMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 23 /r ibAVX10.1 or AVX512F
VSHUFF64X2 ymm {k}{z}, ymm, ymm, imm8 VSHUFF64X2_YMMf64_MASKmskw_YMMf64_YMMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 23 /r ibAVX10.1 or AVX512F + AVX512VL
VSHUFF64X2 ymm {k}{z}, ymm, m256/m64bcst, imm8 VSHUFF64X2_YMMf64_MASKmskw_YMMf64_MEMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 23 /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.
Modelzmm {k}{z}, zmm, zmm, imm8
ymm {k}{z}, ymm, ymm, imm8
zmm {k}{z}, zmm, m512/m64bcst, imm8
ymm {k}{z}, ymm, m256/m64bcst, imm8
Skylake-SP, Ice Lake3 / 1p510 / 1p5
Sapphire Rapids3 / 1p511 / 1p5
Zen 42 / 1FP19 / 1FP1

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.

128-bit blocks by immediate: the low half of the result comes from blocks of zmm2, the high half from blocks of zmm3, each picked by bits of imm8.
VSHUFF64X2 with imm8 = 0x4EWith imm8 = 0x4E, result doubles 7 to 0: b3, unchanged (bit 6 of k1 is 0), b1, b0, a7, a6, a5, a4.0x4Eimm8example01234567zmm2a11111110k1a4a5a6a7b0b1b3zmm101234567zmm3or m512b

Example: imm8 = 0x4E (0100 1110 in binary). Shown for the zmm form; the ymm form works the same on 4 doubles. The 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 zmm3.

With imm8 = 0x4E, result doubles 7 to 0: b3, unchanged (bit 6 of k1 is 0), b1, b0, a7, a6, a5, a4.

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):
    lane = i // 2
    if VL == 256:
        x = imm8 >> lane & 1      # one bit per lane
    else:
        x = imm8 >> 2 * lane & 3  # two bits per lane
    j = x * 2 + i % 2
    if k1[i]:
        if lane < VL // 256:
            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): 4 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
VSHUFF64X2 ymm {k}{z}, ymm, ymm/m256/m64bcst, imm8 VSHUFF64X2 zmm {k}{z}, zmm, zmm/m512/m64bcst, imm8
ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
ymm, zmmexplicitread
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.

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 VSHUFF64X2, 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
_mm512_broadcast_f64x2 __m512d _mm512_broadcast_f64x2(__m128d __A)

VSHUFF64X2 zmm, zmm, zmm, imm8 EVEX.512 -mavx512dq

_mm512_shuffle_f64x2 __m512d _mm512_shuffle_f64x2(__m512d A, __m512d B, const int imm)

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

_mm512_mask_broadcast_f64x2 __m512d _mm512_mask_broadcast_f64x2(__m512d __O, __mmask8 __M, __m128d __A)

VSHUFF64X2 zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512dq

_mm512_mask_shuffle_f64x2 __m512d _mm512_mask_shuffle_f64x2(__m512d W, __mmask8 U, __m512d A, __m512d B, const int imm)

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

_mm512_maskz_broadcast_f64x2 __m512d _mm512_maskz_broadcast_f64x2(__mmask8 __M, __m128d __A)

VSHUFF64X2 zmm {k}{z}, zmm, zmm, imm8 EVEX.512 -mavx512dq

_mm512_maskz_shuffle_f64x2 __m512d _mm512_maskz_shuffle_f64x2(__mmask8 U, __m512d A, __m512d B, const int imm)

VSHUFF64X2 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
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_256

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

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-750 (VSHUFF32x4/VSHUFF64x2/VSHUFI32x4/VSHUFI64x2)
  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.