Instruction
VPERMT2Q
Selects quadwords from two tables with an index vector, the result overwriting the first table.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPERMT2Q fills each quadword of its destination from a table of two registers, the destination itself and the third operand, at the index held in the matching quadword of the second operand. It is the quadword form of VPERMT2D, and VPERMI2Q is its twin that overwrites the indices instead of the table; VPERMI2D explains the pair and the intrinsics that stand for both.
Index bits
With 8 quadwords to a ZMM register, the table holds 16 elements: bits
2:0 of each index choose the element and bit 3 the register, and the
other 60 bits are ignored. YMM and XMM tables hold 8 and 4 elements and
use bits 2:0 and 1:0. The cases recorded on Zen 5 used random 64-bit
indices: 65F2A504C4AFBE7Eh, whose low four bits are 1110b, picked
element 6 of the second register, and F60E43C7B5D831E7h element 7 of
the first. Nothing forbids one register in two roles:
vpermt2q xmm9, xmm9, xmm14 used XMM9 as indices and first table at
once, and its element 0, whose index ended in 00b, came back
unchanged.
In compiled code
Interleaving two int64_t arrays, c[2*i] = re[i]; c[2*i+1] = im[i];,
and the reverse split both take two VPERMT2Qs per pair of registers in
GCC 14 and Clang 23 at -O2 with -march=x86-64-v4, one with the
indices of the low or even halves and one with those of the high or odd
ones; GCC works on ZMM and Clang on YMM registers. As each permute
overwrites a table, one of the two first copies its register. For a
fixed shuffle of two arguments, __builtin_shufflevector(a, b, 0, 8, 1, 9, ...), Clang emits VPERMT2Q over a and GCC VPERMI2Q over the
loaded indices. VPERMT2PD does the same for
doubles.
AMD’s latency spreadsheet for Zen 5 lists VPERMT2Q as VPERMT2D: one macro-op with a latency of 3, 4 and 5 cycles for XMM, YMM and ZMM.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPERMT2Q zmm {k}{z}, zmm, zmm
VPERMT2Q_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512 | EVEX.512.66.0F38.W1 7E /r | AVX10.1 or AVX512F |
VPERMT2Q zmm {k}{z}, zmm, m512/m64bcst
VPERMT2Q_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512 | EVEX.512.66.0F38.W1 7E /r | AVX10.1 or AVX512F |
VPERMT2Q xmm {k}{z}, xmm, xmm
VPERMT2Q_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512 | EVEX.128.66.0F38.W1 7E /r | AVX10.1 or AVX512F + AVX512VL |
VPERMT2Q xmm {k}{z}, xmm, m128/m64bcst
VPERMT2Q_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512 | EVEX.128.66.0F38.W1 7E /r | AVX10.1 or AVX512F + AVX512VL |
VPERMT2Q ymm {k}{z}, ymm, ymm
VPERMT2Q_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512 | EVEX.256.66.0F38.W1 7E /r | AVX10.1 or AVX512F + AVX512VL |
VPERMT2Q ymm {k}{z}, ymm, m256/m64bcst
VPERMT2Q_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512 | EVEX.256.66.0F38.W1 7E /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m64bcstymm {k}{z}, ymm, m256/m64bcst | xmm {k}{z}, xmm, xmm | xmm {k}{z}, xmm, m128/m64bcst | ymm {k}{z}, ymm, ymm |
|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 3 / 1p5 | 10 / 1p5 | 3 / 1p5 | 9 / 1p5 | 3 / 1p5 |
| Sapphire Rapids | 3 / 1p5 | 11 / 1p5 | 3 / 1p5 | 10 / 1p5 | 3 / 1p5 |
| Zen 4 | 5 / 1FP1 FP2 | 8 / 0.5FP1 FP2 | 3 / 11FP1 FP2 | 8 / 0.5FP1 FP2 | 4 / 12FP1 FP2 |
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 index vector in zmm2 (element 0 on the right); only its low 4 bits count. Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 quadwords. Under the mask, a masked-off element keeps the old value of zmm1, the first table.
With the example indices, result quadwords 7 to 0: b7, unchanged (bit 6 of k1 is 0), b1, a6, b6, a0, a1, a3.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
n = VL // 64 # 2 in xmm, 4 in ymm, 8 in zmm
src1 = zmm1.read() # the first table: zmm1 as it was
for i in range(n):
if k1[i]:
x = zmm2.q[i]
if x & n:
zmm1.q[i] = src3.q[x % n]
else:
zmm1.q[i] = src1.q[x % n]
elif zeroing:
zmm1.q[i] = 0
# else: zmm1.q[i] keeps its value
# m64bcst: src3.q[i] is the m64 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPERMT2Q xmm {k}{z}, xmm, xmm/m128/m64bcst VPERMT2Q ymm {k}{z}, ymm, ymm/m256/m64bcst VPERMT2Q zmm {k}{z}, zmm, zmm/m512/m64bcst | ||
xmm, ymm, zmm | explicit | read, write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | 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-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 VPERMT2Q, 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 |
|---|---|
_mm_permutex2var_epi64
__m128i _mm_permutex2var_epi64(__m128i __A, __m128i __I, __m128i __B) |
|
_mm_mask_permutex2var_epi64
__m128i _mm_mask_permutex2var_epi64(__m128i __A, __mmask8 __U, __m128i __I, __m128i __B) |
|
_mm_maskz_permutex2var_epi64
__m128i _mm_maskz_permutex2var_epi64(__mmask8 __U, __m128i __A, __m128i __I, __m128i __B) |
|
_mm256_permutex2var_epi64
__m256i _mm256_permutex2var_epi64(__m256i __A, __m256i __I, __m256i __B) |
|
_mm256_mask_permutex2var_epi64
__m256i _mm256_mask_permutex2var_epi64(__m256i __A, __mmask8 __U, __m256i __I, __m256i __B) |
|
_mm256_maskz_permutex2var_epi64
__m256i _mm256_maskz_permutex2var_epi64(__mmask8 __U, __m256i __A, __m256i __I, __m256i __B) |
|
_mm512_permutex2var_epi64
__m512i _mm512_permutex2var_epi64(__m512i __A, __m512i __I, __m512i __B) |
|
_mm512_mask_permutex2var_epi64
__m512i _mm512_mask_permutex2var_epi64(__m512i __A, __mmask8 __U, __m512i __I, __m512i __B) |
|
_mm512_maskz_permutex2var_epi64
__m512i _mm512_maskz_permutex2var_epi64(__mmask8 __U, __m512i __A, __m512i __I, __m512i __B) |
|
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 |
|---|---|---|
AVX512F_512 | AVX10.1 or 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 or AVX512F + 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_128 | Same as AVX512F_128 |
More AVX10.1 instructions
- VPDPBUSDS
- VPDPWSSD
- VPDPWSSDS
- VPERMB
- VPERMD
- VPERMI2B
- VPERMI2D
- VPERMI2PD
- VPERMI2PS
- VPERMI2Q
- VPERMI2W
- VPERMILPD
- VPERMILPS
- VPERMPD
- VPERMPS
- VPERMQ
- VPERMT2B
- VPERMT2D
- VPERMT2PD
- VPERMT2PS
- VPERMT2W
- VPERMW
- VPEXPANDB
- VPEXPANDD
- VPEXPANDQ
- VPEXPANDW
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPINSRB
- VPINSRD
- VPINSRQ
- VPINSRW
- VPLZCNTD
- VPLZCNTQ
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-535 (VPERMT2W/
D/ Q/ PS/ PD) - 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.