Instruction
VPERMB
Rearranges the bytes of a vector across the whole register using an index vector.
- 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
| Instruction | Encoding | Requires |
|---|---|---|
VPERMB xmm {k}{z}, xmm, xmm
VPERMB_XMMu8_MASKmskw_XMMu8_XMMu8_AVX512 | EVEX.128.66.0F38.W0 8D /r | AVX10.1 or AVX512VBMI + AVX512VL |
VPERMB xmm {k}{z}, xmm, m128
VPERMB_XMMu8_MASKmskw_XMMu8_MEMu8_AVX512 | EVEX.128.66.0F38.W0 8D /r | AVX10.1 or AVX512VBMI + AVX512VL |
VPERMB ymm {k}{z}, ymm, ymm
VPERMB_YMMu8_MASKmskw_YMMu8_YMMu8_AVX512 | EVEX.256.66.0F38.W0 8D /r | AVX10.1 or AVX512VBMI + AVX512VL |
VPERMB ymm {k}{z}, ymm, m256
VPERMB_YMMu8_MASKmskw_YMMu8_MEMu8_AVX512 | EVEX.256.66.0F38.W0 8D /r | AVX10.1 or AVX512VBMI + AVX512VL |
VPERMB zmm {k}{z}, zmm, zmm
VPERMB_ZMMu8_MASKmskw_ZMMu8_ZMMu8_AVX512 | EVEX.512.66.0F38.W0 8D /r | AVX10.1 or AVX512VBMI |
VPERMB zmm {k}{z}, zmm, m512
VPERMB_ZMMu8_MASKmskw_ZMMu8_MEMu8_AVX512 | EVEX.512.66.0F38.W0 8D /r | AVX10.1 or AVX512VBMI |
Latency and throughput
| Model | xmm {k}{z}, xmm, xmmno mask | xmm {k}{z}, xmm, xmmwith a mask, zeroing | xmm {k}{z}, xmm, m128no mask | xmm {k}{z}, xmm, m128with a mask, zeroingymm {k}{z}, ymm, m256with a mask, zeroingzmm {k}{z}, zmm, m512with a mask, zeroing | ymm {k}{z}, ymm, ymmno mask | ymm {k}{z}, ymm, ymmwith a mask, zeroing | ymm {k}{z}, ymm, m256no maskzmm {k}{z}, zmm, m512no mask | zmm {k}{z}, zmm, zmmno mask | zmm {k}{z}, zmm, zmmwith a mask, zeroing |
|---|---|---|---|---|---|---|---|---|---|
| Ice Lake | 3 / 1p5 | 3 / 1p5 | 10 / 1p5 | 10 / 1p5 | 3 / 1p5 | 3 / 1p5 | 10 / 1p5 | 3 / 1p5 | 3 / 1p5 |
| Sapphire Rapids | 3 / 1p5 | 5 / 1p5 | 10 / 1p5 | 13 / 1p5 | 3 / 1p5 | 5 / 1p5 | 11 / 1p5 | 3 / 1p5 | 5 / 1p5 |
| Zen 4 | 2 / 11FP1 FP2 | 2 / 11FP1 FP2 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 4 / 12FP1 FP2 | 4 / 12FP1 FP2 | 8 / 0.5FP1 FP2 | 5 / 1FP1 FP2 | 5 / 1FP1 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 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 upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPERMB xmm {k}{z}, xmm, xmm/m128 VPERMB ymm {k}{z}, ymm, ymm/m256 VPERMB zmm {k}{z}, zmm, zmm/m512 | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128, ymm/m256, zmm/m512 | 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
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.
| Intrinsic | Compiles to |
|---|---|
_mm_permutexvar_epi8
__m128i _mm_permutexvar_epi8(__m128i __A, __m128i __B) |
|
_mm_mask_permutexvar_epi8
__m128i _mm_mask_permutexvar_epi8(__m128i __W, __mmask16 __M, __m128i __A, __m128i __B) |
|
_mm_maskz_permutexvar_epi8
__m128i _mm_maskz_permutexvar_epi8(__mmask16 __M, __m128i __A, __m128i __B) |
|
_mm256_permutexvar_epi8
__m256i _mm256_permutexvar_epi8(__m256i __A, __m256i __B) |
|
_mm256_mask_permutexvar_epi8
__m256i _mm256_mask_permutexvar_epi8(__m256i __W, __mmask32 __M, __m256i __A, __m256i __B) |
|
_mm256_maskz_permutexvar_epi8
__m256i _mm256_maskz_permutexvar_epi8(__mmask32 __M, __m256i __A, __m256i __B) |
|
_mm512_permutexvar_epi8
__m512i _mm512_permutexvar_epi8(__m512i __A, __m512i __B) |
|
_mm512_mask_permutexvar_epi8
__m512i _mm512_mask_permutexvar_epi8(__m512i __W, __mmask64 __M, __m512i __A, __m512i __B) |
|
_mm512_maskz_permutexvar_epi8
__m512i _mm512_maskz_permutexvar_epi8(__mmask64 __M, __m512i __A, __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 |
|---|---|---|
AVX512_VBMI_128 | AVX10.1 or AVX512VBMI + 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_128 | Same as AVX512_VBMI_128 |
AVX512_VBMI_512 | AVX10.1 or AVX512VBMI | Same as AVX512_VBMI_128 |
More AVX10.1 instructions
- VPCMPGTB
- VPCMPGTD
- VPCMPGTQ
- VPCMPGTW
- VPCMPQ
- VPCMPUB
- VPCMPUD
- VPCMPUQ
- VPCMPUW
- VPCMPW
- VPCOMPRESSB
- VPCOMPRESSD
- VPCOMPRESSQ
- VPCOMPRESSW
- VPCONFLICTD
- VPCONFLICTQ
- VPDPBUSD
- VPDPBUSDS
- VPDPWSSD
- VPDPWSSDS
- VPERMD
- VPERMI2B
- VPERMI2D
- VPERMI2PD
- VPERMI2PS
- VPERMI2Q
- VPERMI2W
- VPERMILPD
- VPERMILPS
- VPERMPD
- VPERMPS
- VPERMQ
- VPERMT2B
- VPERMT2D
- VPERMT2PD
- VPERMT2PS
- VPERMT2Q
- VPERMT2W
- VPERMW
- VPEXPANDB
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-498 (VPERMB)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
- 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.