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

VPERMT2W fills each word of its destination from a table of two registers, the destination itself and the third operand, at the index held in the matching word of the second operand. It is the word form of VPERMT2D, which explains why the T form keeps its indices and overwrites the table, and VPERMI2W is the twin that overwrites the indices. It needs AVX512BW, where VPERMT2B needs AVX512_VBMI, and has no broadcast form.

Index bits

A ZMM table holds 64 words, so bits 5:0 of each index count, bit 5 choosing the register; YMM and XMM tables use bits 4:0 and 3:0, and the higher bits are ignored. In the recorded Zen 5 case vpermt2w xmm14, xmm8, xmm29, index BD34h picked word 4 of XMM14, D661h word 1, 8638h word 0 of XMM29 and E19Ah word 2 of XMM29; the register above the eight words was cleared. In vpermt2w zmm5{k5}, zmm5, zmm5, where one register is index and both tables, every index was read before any element was written.

In compiled code

Taking the even and the odd words apart, ev[i] = s[2*i] and od[i] = s[2*i+1] over int16_t arrays, is one VPERMT2W per output vector in GCC 14 and Clang 23 at -O2 with -march=x86-64-v4, with the index vectors 0, 2, 4 … and 1, 3, 5 … loaded once before the loop: GCC on ZMM and Clang on YMM registers, each copying the first table first because the permute overwrites it. GCC narrows doublewords to words the same way, a VPERMT2W of two loads picking the low halves, where Clang uses VPMOVDW. _mm512_permutex2var_epi16 and its _mask_ form are VPERMT2W in GCC; the _mask2_ form, which merges into the indices, is VPERMI2W.

AMD’s Zen 5 latency spreadsheet gives VPERMT2W one macro-op on FP1 or FP2, with 3, 4 and 5 cycles of latency for XMM, YMM and ZMM, as VPERMT2B.

Forms

Every encoding of VPERMT2W that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPERMT2W xmm {k}{z}, xmm, xmm VPERMT2W_XMMu16_MASKmskw_XMMu16_XMMu16_AVX512EVEX.128.66.0F38.W1 7D /rAVX10.1 or AVX512BW + AVX512VL
VPERMT2W xmm {k}{z}, xmm, m128 VPERMT2W_XMMu16_MASKmskw_XMMu16_MEMu16_AVX512EVEX.128.66.0F38.W1 7D /rAVX10.1 or AVX512BW + AVX512VL
VPERMT2W ymm {k}{z}, ymm, ymm VPERMT2W_YMMu16_MASKmskw_YMMu16_YMMu16_AVX512EVEX.256.66.0F38.W1 7D /rAVX10.1 or AVX512BW + AVX512VL
VPERMT2W ymm {k}{z}, ymm, m256 VPERMT2W_YMMu16_MASKmskw_YMMu16_MEMu16_AVX512EVEX.256.66.0F38.W1 7D /rAVX10.1 or AVX512BW + AVX512VL
VPERMT2W zmm {k}{z}, zmm, zmm VPERMT2W_ZMMu16_MASKmskw_ZMMu16_ZMMu16_AVX512EVEX.512.66.0F38.W1 7D /rAVX10.1 or AVX512BW
VPERMT2W zmm {k}{z}, zmm, m512 VPERMT2W_ZMMu16_MASKmskw_ZMMu16_MEMu16_AVX512EVEX.512.66.0F38.W1 7D /rAVX10.1 or AVX512BW

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}, xmm, xmmno maskxmm {k}{z}, xmm, xmmwith a mask, zeroingxmm {k}{z}, xmm, m128no maskxmm {k}{z}, xmm, m128with a mask, zeroingymm {k}{z}, ymm, ymmno maskymm {k}{z}, ymm, ymmwith a mask, zeroingymm {k}{z}, ymm, m256no maskymm {k}{z}, ymm, m256with a mask, zeroingzmm {k}{z}, zmm, zmmno maskzmm {k}{z}, zmm, zmmwith a mask, zeroingzmm {k}{z}, zmm, m512no maskzmm {k}{z}, zmm, m512with a mask, zeroing
Skylake-SP, Ice Lake7 / 2p0157 / 2p01513 / 2p01513 / 2p0157 / 2p0157 / 2p01514 / 2p01514 / 2p0157 / 2p0157 / 2p01514 / 2p01514 / 2p015
Sapphire Rapids7 / 2p0159 / 2p01513 / 2p01515 / 2p0157 / 2p0159 / 2p01514 / 2p01516 / 2p0157 / 2p059 / 2p0514 / 2p0516 / 2p05
Zen 43 / 1FP1 FP23 / 1FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP24 / 1FP1 FP24 / 1FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP25 / 1FP1 FP25 / 1FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 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.

Permute from two tables: each word of the result is the word that the index in the same place of ymm2 numbers in ymm1 or, with the index's next bit set, in ymm3.
VPERMT2W with an example index vectorWith the example indices, result words 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, a10, a1, b5, b12, a5, a15, b2, a9, b6, b14, a0, b1, a3.317030229181552821110231324ymm2index0135910131524678111214ymm1a1111111111111110k1a3a0a9a15a5a1a10b1b14b6b2b12b5b7b8ymm10349101113151256781214ymm3or m256b

Example index vector in ymm2 (element 0 on the right); only its low 5 bits count. Shown for the ymm form; the xmm and zmm forms work the same on 8 and 32 words. Under the mask, a masked-off element keeps the old value of ymm1, the first table.

With the example indices, result words 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, a10, a1, b5, b12, a5, a15, b2, a9, b6, b14, a0, b1, a3.

Operation

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

n = VL // 16        # 8 in xmm, 16 in ymm, 32 in zmm
src1 = zmm1.read()  # the first table: zmm1 as it was
for i in range(n):
    if k1[i]:
        x = zmm2.w[i]
        if x & n:
            zmm1.w[i] = src3.w[x % n]
        else:
            zmm1.w[i] = src1.w[x % n]
    elif zeroing:
        zmm1.w[i] = 0
    # else: zmm1.w[i] keeps its value
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 6 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
VPERMT2W xmm {k}{z}, xmm, xmm/m128 VPERMT2W ymm {k}{z}, ymm, ymm/m256 VPERMT2W zmm {k}{z}, zmm, zmm/m512
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128, ymm/m256, zmm/m512explicitread

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

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPERMT2W, 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
_mm_permutex2var_epi16 __m128i _mm_permutex2var_epi16(__m128i __A, __m128i __I, __m128i __B)

VPERMT2W xmm, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm_permutex2var_pbh __m128bh _mm_permutex2var_pbh(__m128bh __A, __m128i __I, __m128bh __B)

VPERMT2W xmm, xmm, xmm EVEX.128 -mavx10.2

_mm_permutex2var_ph __m128h _mm_permutex2var_ph(__m128h __A, __m128i __I, __m128h __B)

VPERMT2W xmm, xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_mask_permutex2var_epi16 __m128i _mm_mask_permutex2var_epi16(__m128i __A, __mmask8 __U, __m128i __I, __m128i __B)

VPERMT2W xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm_maskz_permutex2var_epi16 __m128i _mm_maskz_permutex2var_epi16(__mmask8 __U, __m128i __A, __m128i __I, __m128i __B)

VPERMT2W xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm256_permutex2var_epi16 __m256i _mm256_permutex2var_epi16(__m256i __A, __m256i __I, __m256i __B)

VPERMT2W ymm, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm256_permutex2var_pbh __m256bh _mm256_permutex2var_pbh(__m256bh __A, __m256i __I, __m256bh __B)

VPERMT2W ymm, ymm, ymm EVEX.256 -mavx10.2

_mm256_permutex2var_ph __m256h _mm256_permutex2var_ph(__m256h __A, __m256i __I, __m256h __B)

VPERMT2W ymm, ymm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_permutex2var_epi16 __m256i _mm256_mask_permutex2var_epi16(__m256i __A, __mmask16 __U, __m256i __I, __m256i __B)

VPERMT2W ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm256_maskz_permutex2var_epi16 __m256i _mm256_maskz_permutex2var_epi16(__mmask16 __U, __m256i __A, __m256i __I, __m256i __B)

VPERMT2W ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm512_permutex2var_epi16 __m512i _mm512_permutex2var_epi16(__m512i __A, __m512i __I, __m512i __B)

VPERMT2W zmm, zmm, zmm EVEX.512 -mavx512bw

_mm512_permutex2var_pbh __m512bh _mm512_permutex2var_pbh(__m512bh __A, __m512i __I, __m512bh __B)

VPERMT2W zmm, zmm, zmm EVEX.512 -mavx10.2

_mm512_permutex2var_ph __m512h _mm512_permutex2var_ph(__m512h __A, __m512i __I, __m512h __B)

VPERMT2W zmm, zmm, zmm EVEX.512 -mavx512fp16

_mm512_mask_permutex2var_epi16 __m512i _mm512_mask_permutex2var_epi16(__m512i __A, __mmask32 __U, __m512i __I, __m512i __B)

VPERMT2W zmm {k}, zmm, zmm EVEX.512 -mavx512bw

_mm512_maskz_permutex2var_epi16 __m512i _mm512_maskz_permutex2var_epi16(__mmask32 __U, __m512i __A, __m512i __I, __m512i __B)

VPERMT2W zmm {k}{z}, zmm, zmm EVEX.512 -mavx512bw

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
AVX512BW_128

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

or

AVX512BW + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW
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
AVX512BW_256
Same as AVX512BW_128Same as AVX512BW_128
AVX512BW_512

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

or

AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW

Same as AVX512BW_128

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-535 (VPERMT2W/D/Q/PS/PD)
  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.