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

VPERMB builds each byte of its result by picking a byte of a table: the index byte in the same position of the first source says which byte of the second source to take. It came with AVX512_VBMI and is the first byte permute of x86 that reaches across the whole register, 16, 32 or 64 bytes, where PSHUFB and its VEX and EVEX forms pick only within each 128-bit lane.

How the index is read

Only the low bits of an index count: 4 in the xmm form, 5 in ymm, 6 in zmm. The bits above are ignored, bit 7 included, so no index gives a zero byte as PSHUFB’s bit 7 does; a zero comes from the write mask with {z} instead. In a case recorded on Zen 5 with the xmm form, the index bytes C0h and A0h both took byte 0 of the table, and 57h and C7h both byte 7. The operand order differs from PSHUFB’s too: the indices are the first source and the table is the one that may be in memory, as in VPERMD and the intrinsic _mm512_permutexvar_epi8(idx, table).

Where it appears

With -mavx512vbmi, or a processor that has it such as -march=znver5 or -march=icelake-server, GCC 14 and Clang 23 at -O2 compile a constant shuffle that reverses the 64 bytes of a vector to one VPERMB with the indices loaded from memory. -march=x86-64-v4 does not include VBMI, and there the same shuffle takes two or more instructions of AVX512BW: Clang reverses within lanes with VPSHUFB and swaps the lanes with VSHUFI64X2, and GCC uses VPERMW, two VPSHUFBs and an OR.

Neither compiler turns a table lookup loop such as out[i] = table[in[i] & 63] into VPERMB. Intel’s optimization guide writes it by hand, with the 64-byte table held in a register and one VPERMB per 64 input bytes, and reports it 6.5 times as fast as an AVX512BW version that widens the bytes to words (Section 17.17.1, Example 17-26). The same chapter pairs VPERMB with VPMULTISHIFTQB to unpack 5-bit fields. A table of 128 bytes needs VPERMI2B or VPERMT2B, which index two registers with 7 bits.

AMD’s Zen 5 guide lists VPERMB as one macro-op with a latency of 2, 4 and 5 cycles for the xmm, ymm and zmm forms.

In the optimization guide

What the optimization guide says about VPERMB, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Vectors

  • Shuffles and lane crossing: AVX-512’s two-source permutes and VBMI’s VPERMB take any element of their sources, each in one macro-op on Zen 5.

Forms

Every encoding of VPERMB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPERMB xmm {k}{z}, xmm, xmm VPERMB_XMMu8_MASKmskw_XMMu8_XMMu8_AVX512EVEX.128.66.0F38.W0 8D /rAVX10.1 or AVX512VBMI + AVX512VL
VPERMB xmm {k}{z}, xmm, m128 VPERMB_XMMu8_MASKmskw_XMMu8_MEMu8_AVX512EVEX.128.66.0F38.W0 8D /rAVX10.1 or AVX512VBMI + AVX512VL
VPERMB ymm {k}{z}, ymm, ymm VPERMB_YMMu8_MASKmskw_YMMu8_YMMu8_AVX512EVEX.256.66.0F38.W0 8D /rAVX10.1 or AVX512VBMI + AVX512VL
VPERMB ymm {k}{z}, ymm, m256 VPERMB_YMMu8_MASKmskw_YMMu8_MEMu8_AVX512EVEX.256.66.0F38.W0 8D /rAVX10.1 or AVX512VBMI + AVX512VL
VPERMB zmm {k}{z}, zmm, zmm VPERMB_ZMMu8_MASKmskw_ZMMu8_ZMMu8_AVX512EVEX.512.66.0F38.W0 8D /rAVX10.1 or AVX512VBMI
VPERMB zmm {k}{z}, zmm, m512 VPERMB_ZMMu8_MASKmskw_ZMMu8_MEMu8_AVX512EVEX.512.66.0F38.W0 8D /rAVX10.1 or AVX512VBMI

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, zeroing
ymm {k}{z}, ymm, m256with a mask, zeroing
zmm {k}{z}, zmm, m512with a mask, zeroing
ymm {k}{z}, ymm, ymmno maskymm {k}{z}, ymm, ymmwith a mask, zeroingymm {k}{z}, ymm, m256no mask
zmm {k}{z}, zmm, m512no mask
zmm {k}{z}, zmm, zmmno maskzmm {k}{z}, zmm, zmmwith a mask, zeroing
Ice Lake3 / 1p53 / 1p510 / 1p510 / 1p53 / 1p53 / 1p510 / 1p53 / 1p53 / 1p5
Sapphire Rapids3 / 1p55 / 1p510 / 1p513 / 1p53 / 1p55 / 1p511 / 1p53 / 1p55 / 1p5
Zen 42 / 11FP1 FP22 / 11FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP24 / 12FP1 FP24 / 12FP1 FP28 / 0.5FP1 FP25 / 1FP1 FP25 / 1FP1 FP2
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2223; AMD 58455, row 571).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2224; AMD 58455, row 572).

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 by index: each byte of the result is the byte of the table xmm3 that the index in the same place of xmm2 numbers, across the whole register.
VPERMB with an example index vectorWith the example indices, result bytes 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, b10, b1, b5, b12, b5, b15, b2, b9, b6, b14, b0, b11, b3.0123567891011121314154xmm3or m128b1111111111111110k1b3b11b0b14b6b9b2b15b5b12b5b1b10b7b8xmm13110146921551251107138xmm2index

Example index vector in xmm2 (element 0 on the right); only its low 4 bits count. Shown for the xmm form; the ymm and zmm forms work the same on 32 and 64 bytes. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

With the example indices, result bytes 15 to 0: b8, unchanged (bit 14 of k1 is 0), b7, b10, b1, b5, b12, b5, b15, b2, b9, b6, b14, b0, b11, b3.

Operation

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

n = VL // 8  # 16 in xmm, 32 in ymm, 64 in zmm
for i in range(n):
    if k1[i]:
        zmm1.b[i] = src3.b[zmm2.b[i] % n]
    elif zeroing:
        zmm1.b[i] = 0
    # else: zmm1.b[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
VPERMB xmm {k}{z}, xmm, xmm/m128 VPERMB ymm {k}{z}, ymm, ymm/m256 VPERMB zmm {k}{z}, zmm, zmm/m512
xmm, ymm, zmmexplicitwrite (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 VPERMB, 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_permutexvar_epi8 __m128i _mm_permutexvar_epi8(__m128i __A, __m128i __B)

VPERMB xmm, xmm, xmm EVEX.128 -mavx512vbmi -mavx512vl

_mm_mask_permutexvar_epi8 __m128i _mm_mask_permutexvar_epi8(__m128i __W, __mmask16 __M, __m128i __A, __m128i __B)

VPERMB xmm {k}, xmm, xmm EVEX.128 -mavx512vbmi -mavx512vl

_mm_maskz_permutexvar_epi8 __m128i _mm_maskz_permutexvar_epi8(__mmask16 __M, __m128i __A, __m128i __B)

VPERMB xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vbmi -mavx512vl

_mm256_permutexvar_epi8 __m256i _mm256_permutexvar_epi8(__m256i __A, __m256i __B)

VPERMB ymm, ymm, ymm EVEX.256 -mavx512vbmi -mavx512vl

_mm256_mask_permutexvar_epi8 __m256i _mm256_mask_permutexvar_epi8(__m256i __W, __mmask32 __M, __m256i __A, __m256i __B)

VPERMB ymm {k}, ymm, ymm EVEX.256 -mavx512vbmi -mavx512vl

_mm256_maskz_permutexvar_epi8 __m256i _mm256_maskz_permutexvar_epi8(__mmask32 __M, __m256i __A, __m256i __B)

VPERMB ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vbmi -mavx512vl

_mm512_permutexvar_epi8 __m512i _mm512_permutexvar_epi8(__m512i __A, __m512i __B)

VPERMB zmm, zmm, zmm EVEX.512 -mavx512vbmi

_mm512_mask_permutexvar_epi8 __m512i _mm512_mask_permutexvar_epi8(__m512i __W, __mmask64 __M, __m512i __A, __m512i __B)

VPERMB zmm {k}, zmm, zmm EVEX.512 -mavx512vbmi

_mm512_maskz_permutexvar_epi8 __m512i _mm512_maskz_permutexvar_epi8(__mmask64 __M, __m512i __A, __m512i __B)

VPERMB zmm {k}{z}, zmm, zmm EVEX.512 -mavx512vbmi

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
AVX512_VBMI_128

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

or

AVX512VBMI + AVX512VL
CPUID.(EAX=07H,ECX=0):ECX[1] AVX512VBMI
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512_VBMI_256
Same as AVX512_VBMI_128Same as AVX512_VBMI_128
AVX512_VBMI_512

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

or

AVX512VBMI
CPUID.(EAX=07H,ECX=0):ECX[1] AVX512VBMI

Same as AVX512_VBMI_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-498 (VPERMB)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  8. 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.