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

VEXTRACTI64X2 is VEXTRACTI32X4 with a mask of quadwords: it copies one 128-bit block of a YMM or ZMM register, chosen by bits 1:0 of the immediate (bit 0 for YMM), to an XMM register or to 16 bytes of memory. It needs AVX512DQ (and AVX512VL for a YMM source), where VEXTRACTI32X4 needs only AVX512F. Unmasked the two give the same result, and the VEXTRACTI32X4 page covers the register and memory forms.

On Zen 5, vextracti64x2 xmm0{k2}, zmm31, 7 took block 3, the top 16 bytes of ZMM31, and with 01b in the low bits of K2 wrote its first quadword and kept the second of XMM0. A fully masked store wrote nothing: vextracti64x2 [mem]{k6}, zmm1, 0BEh with 00b in the low bits of K6 left the 16 bytes as they were.

In compiled code

GCC 14 at -O2 with -march=x86-64-v4 uses VEXTRACTI64X2 in the last steps of a reduction: after VEXTRACTI64X4 has folded a zmm register to ymm, VEXTRACTI64X2 of the high half of that ymm register folds it to xmm. It does so for the sum or XOR of long long elements in a loop and for _mm512_reduce_add_epi32 and _mm512_reduce_add_epi64. Clang 23 emits VEXTRACTI128 at that step, and with -mavx512f alone, which lacks AVX512DQ and AVX512VL, GCC does too.

Masked, _mm512_mask_extracti64x2_epi64 is VEXTRACTI64X2 in both compilers. Unmasked, Clang extracts block 1 of a zmm register with VEXTRACTF128 of its low ymm half, which needs only AVX.

AMD’s Zen 5 latency spreadsheet gives it the timings of VEXTRACTI32X4: three cycles from a YMM register, five from a ZMM register, one more for the memory forms, two per cycle. Zen 5’s 4 recorded cases cover the register and memory forms at both widths.

Forms

Every encoding of VEXTRACTI64X2 that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VEXTRACTI64X2 xmm {k}{z}, ymm, imm8 VEXTRACTI64X2_XMMu64_MASKmskw_YMMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 39 /r ibAVX10.1 or AVX512DQ + AVX512VL
VEXTRACTI64X2 m128 {k}, ymm, imm8 VEXTRACTI64X2_MEMu64_MASKmskw_YMMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 39 /r ibAVX10.1 or AVX512DQ + AVX512VL
VEXTRACTI64X2 xmm {k}{z}, zmm, imm8 VEXTRACTI64X2_XMMu64_MASKmskw_ZMMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 39 /r ibAVX10.1 or AVX512DQ
VEXTRACTI64X2 m128 {k}, zmm, imm8 VEXTRACTI64X2_MEMu64_MASKmskw_ZMMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 39 /r ibAVX10.1 or AVX512DQ

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 {k}{z}, ymm, imm8
xmm {k}{z}, zmm, imm8
m128 {k}, ymm, imm8
m128 {k}, zmm, imm8
Skylake-SP3 / 1p51 / 1p2347
Ice Lake3 / 1p51 / 0.5p4789
Sapphire Rapids3 / 1p512 / 0.5p4789
Zen 41 / 11FP11 / 1FP45 FPSt LSU Store
  1. Zen 4 model, ymm form: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 1148; AMD 58455, row 533).

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.

Extract: the 128-bit block of zmm2 that imm8 numbers goes to xmm1.Register forms
VEXTRACTI64X2 with imm8 = 0x02With imm8 = 0x02, result quadwords 1 to 0: a5, a4.01236745zmm2a11k1a4a5xmm1

Example: imm8 = 0x02. Shown for the zmm form; the ymm form works the same on 4 quadwords. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

With imm8 = 0x02, result quadwords 1 to 0: a5, a4.

Extract: the 128-bit block of zmm2 that imm8 numbers goes to m128.Memory forms
VEXTRACTI64X2 with imm8 = 0x02With imm8 = 0x02, result quadwords 1 to 0: a5, a4.m128

Example: imm8 = 0x02. Shown for the zmm form; the ymm form works the same on 4 quadwords. The forms write under a mask: where its bit is 0, the element keeps its old value.

With imm8 = 0x02, result quadwords 1 to 0: a5, a4.

Operation

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

Register forms
x = imm8 & (VL // 128 - 1)  # the 128-bit block
for i in range(2):
    if k1[i]:
        xmm1.q[i] = zmm2.q[x * 2 + i]
    elif zeroing:
        xmm1.q[i] = 0
    # else: xmm1.q[i] keeps its value
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 2 cases.

Memory forms
x = imm8 & (VL // 128 - 1)  # the 128-bit block
for i in range(2):
    if k1[i]:
        mem.q[i] = zmm2.q[x * 2 + i]
    # else: mem.q[i] is not written

Run on AMD Zen 5 (EPYC 9645): 2 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
VEXTRACTI64X2 xmm/m128 {k}{z}, ymm, imm8 VEXTRACTI64X2 xmm/m128 {k}{z}, zmm, imm8
xmm/m128explicitwrite (masked)
{k}explicitread (write mask)
ymm, zmmexplicitread
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-E6NF

Attributes

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

All forms
write masking

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VEXTRACTI64X2, 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_mask_extracti64x2_epi64 __m128i _mm256_mask_extracti64x2_epi64(__m128i W, __mmask8 U, __m256i A, const int imm)

VEXTRACTI64X2 xmm {k}, ymm, imm8 EVEX.256 -mavx512vl -mavx512dq

_mm256_maskz_extracti64x2_epi64 __m128i _mm256_maskz_extracti64x2_epi64(__mmask8 U, __m256i A, const int imm)

VEXTRACTI64X2 xmm {k}{z}, ymm, imm8 EVEX.256 -mavx512vl -mavx512dq

_mm512_extracti64x2_epi64 __m128i _mm512_extracti64x2_epi64(__m512i A, const int imm)

VEXTRACTI64X2 xmm, zmm, imm8 EVEX.512 -mavx512dqClang emits the equivalent VEXTRACTI32X4

_mm512_mask_extracti64x2_epi64 __m128i _mm512_mask_extracti64x2_epi64(__m128i W, __mmask8 U, __m512i A, const int imm)

VEXTRACTI64X2 xmm {k}, zmm, imm8 EVEX.512 -mavx512dq

_mm512_maskz_extracti64x2_epi64 __m128i _mm512_maskz_extracti64x2_epi64(__mmask8 U, __m512i A, const int imm)

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

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
AVX512DQ_256

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512DQ + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ
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
AVX512DQ_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512DQ
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ

Same as AVX512DQ_256

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-174 (VEXTRACTI128/VEXTRACTI32x4/VEXTRACTI64x2/VEXTRACTI32x8/VEXTRACTI64x4)
  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.