Instruction
VINSERTI64X2
Replaces the 128-bit block that an immediate selects with two quadwords from a register or memory.
- Extensions
- Forms
- 4 (4 EVEX)
- Data
- Intel XED v2026.08.23
VINSERTI64X2 copies a YMM or ZMM source to the destination with one 128-bit block replaced by 16 bytes from an XMM register or memory, then writes the result under a mask of quadwords. It is VINSERTI32X4 with a quadword mask, which that page names as its only difference; the block is chosen the same way, by bits 1:0 of the immediate in a ZMM register and bit 0 in a YMM one, and it needs AVX512DQ where VINSERTI32X4 needs only AVX-512F.
Recorded on Zen 5
- Immediate bits ignored.
vinserti64x2 ymm14, ymm8, xmmword ptr [mem], 0x1aused bit 0 of 1Ah, 0, and put the memory quadwords in the low half, with YMM8’s high half above them and bits 511:256 cleared. - Quadword mask, zeroing.
vinserti64x2 ymm0{k5}{z}, ymm31, xmm16, 0xecput XMM16 in the low half, but with only bit 0 of the four that count set in K5 it wrote quadword 0 alone and zeroed the other three. - Merging. In
vinserti64x2 zmm14{k6}, zmm8, xmm29, 0x3c, K6’s low byte A4h selected quadwords 2, 5 and 7, all from the ZMM8 copy; ZMM14 kept its other five.
In compiled code
GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 compile the masked
intrinsics _mm512_mask_inserti64x2 and _mm256_maskz_inserti64x2 to
VINSERTI64X2. Unmasked, GCC keeps VINSERTI64X2 for
_mm512_inserti64x2 and for _mm256_inserti64x2, where the
EVEX encoding does what the VEX VINSERTI128
does; Clang emits VINSERTF32X4 and
VINSERTF128 there, the same bits under other
names.
AMD’s Zen 5 latency spreadsheet gives VINSERTI64X2 one cycle and two per cycle on pipes FP1 and FP2, as VINSERTI32X4.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VINSERTI64X2 ymm {k}{z}, ymm, xmm, imm8
VINSERTI64X2_YMMu64_MASKmskw_YMMu64_XMMu64_IMM8_AVX512 | EVEX.256.66.0F3A.W1 38 /r ib | AVX10.1 or AVX512DQ + AVX512VL |
VINSERTI64X2 ymm {k}{z}, ymm, m128, imm8
VINSERTI64X2_YMMu64_MASKmskw_YMMu64_MEMu64_IMM8_AVX512 | EVEX.256.66.0F3A.W1 38 /r ib | AVX10.1 or AVX512DQ + AVX512VL |
VINSERTI64X2 zmm {k}{z}, zmm, xmm, imm8
VINSERTI64X2_ZMMu64_MASKmskw_ZMMu64_XMMu64_IMM8_AVX512 | EVEX.512.66.0F3A.W1 38 /r ib | AVX10.1 or AVX512DQ |
VINSERTI64X2 zmm {k}{z}, zmm, m128, imm8
VINSERTI64X2_ZMMu64_MASKmskw_ZMMu64_MEMu64_IMM8_AVX512 | EVEX.512.66.0F3A.W1 38 /r ib | AVX10.1 or AVX512DQ |
Latency and throughput
| Model | ymm {k}{z}, ymm, xmm, imm8zmm {k}{z}, zmm, xmm, imm8 | ymm {k}{z}, ymm, m128, imm8 | zmm {k}{z}, zmm, m128, imm8 |
|---|---|---|---|
| Skylake-SP, Ice Lake | 3 / 1p5 | 8 / 0.5p015 | 8 / 0.5p015 |
| Sapphire Rapids | 3 / 1p5 | 9 / 0.33p015 | 9 / 0.5p05 |
| Zen 4 | 1 / 1FP1 | 8 / 1FP1 | 8 / 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.
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 7 to 0: a7, unchanged (bit 6 of k1 is 0), b1, b0, a3, a2, a1, a0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
x = imm8 & (VL // 128 - 1) # the 128-bit block replaced
for i in range(VL // 64):
if k1[i]:
if i // 2 == x:
zmm1.q[i] = src3.q[i % 2]
else:
zmm1.q[i] = zmm2.q[i]
elif zeroing:
zmm1.q[i] = 0
# else: zmm1.q[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 4 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VINSERTI64X2 ymm {k}{z}, ymm, xmm/m128, imm8 VINSERTI64X2 zmm {k}{z}, zmm, xmm/m128, imm8 | ||
ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
ymm, zmm | explicit | read |
xmm/m128 | explicit | read |
imm8 | explicit | read |
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 VINSERTI64X2, 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.
| Intrinsic | Compiles to |
|---|---|
_mm256_mask_broadcast_i64x2
__m256i _mm256_mask_broadcast_i64x2(__m256i __O, __mmask8 __M, __m128i __A) |
|
_mm256_mask_inserti64x2
__m256i _mm256_mask_inserti64x2(__m256i W, __mmask8 U, __m256i A, __m128i B, const int imm) |
|
_mm256_maskz_broadcast_i64x2
__m256i _mm256_maskz_broadcast_i64x2(__mmask8 __M, __m128i __A) |
|
_mm256_maskz_inserti64x2
__m256i _mm256_maskz_inserti64x2(__mmask8 U, __m256i A, __m128i B, const int imm) |
|
_mm512_inserti64x2
__m512i _mm512_inserti64x2(__m512i A, __m128i B, const int imm) |
|
_mm512_mask_inserti64x2
__m512i _mm512_mask_inserti64x2(__m512i W, __mmask8 U, __m512i A, __m128i B, const int imm) |
|
_mm512_maskz_inserti64x2
__m512i _mm512_maskz_inserti64x2(__mmask8 U, __m512i A, __m128i B, const int imm) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512DQ_256 | AVX10.1 or AVX512DQ + 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 or AVX512DQ | Same as AVX512DQ_256 |
More AVX10.1 instructions
- VGETEXPPH
- VGETEXPPS
- VGETEXPSD
- VGETEXPSH
- VGETEXPSS
- VGETMANTPD
- VGETMANTPH
- VGETMANTPS
- VGETMANTSD
- VGETMANTSH
- VGETMANTSS
- VGF2P8AFFINEINVQB
- VGF2P8AFFINEQB
- VGF2P8MULB
- VINSERTF32X4
- VINSERTF32X8
- VINSERTF64X2
- VINSERTF64X4
- VINSERTI32X4
- VINSERTI32X8
- VINSERTI64X4
- VINSERTPS
- VMAXPD
- VMAXPH
- VMAXPS
- VMAXSD
- VMAXSH
- VMAXSS
- VMINPD
- VMINPH
- VMINPS
- VMINSD
- VMINSH
- VMINSS
- VMOVAPD
- VMOVAPS
- VMOVD
- VMOVDDUP
- VMOVDQA32
- VMOVDQA64
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-411 (VINSERTI128/
VINSERTI32x4/ VINSERTI64x2/ VINSERTI32x8/ VINSERTI64x4) - 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.