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

VPCOMPRESSB packs the bytes that a mask selects into the low end of its destination, in their original order. It is the byte version of VPCOMPRESSD, whose page explains left-packing and how the register and memory destinations differ; AVX512_VBMI2 added it together with VPCOMPRESSW for words and the reverse operations, VPEXPANDB and VPEXPANDW. Before VBMI2, AVX-512 could compress only doublewords and quadwords, so packing bytes took several instructions per vector.

Filtering text

Bytes are what text is made of, so the typical use is dropping characters from a string: compare 64 bytes against a space with VPCMPB into a mask register, compress the bytes whose bits are set, store them, and advance the output by the number kept. The mask has one bit per byte, all 64 bits of a mask register for a ZMM source, so it moves to a general-purpose register with KMOVQ and is counted with POPCNT on 64 bits.

Compilers leave this to the programmer. GCC 14 and Clang 23 at -O2 emit VPCOMPRESSB for the intrinsics _mm512_maskz_compress_epi8 and _mm512_mask_compressstoreu_epi8 once VBMI2 is enabled, with -mavx512vbmi2 or a -march such as icelake-server, znver4 or znver5 (x86-64-v4 does not include it). Neither vectorized the loop if (s[i] != ' ') d[j++] = s[i];, even at -O3 for znver5: both kept it scalar.

The memory form on Zen 5

AMD’s Zen 5 guide lists the register form as two macro-ops with a latency of 2, 4 and 5 cycles for xmm, ymm and zmm, and the memory form, like every compress to memory, as microcoded. The register form followed by an ordinary store is the usual alternative: it writes a whole vector, so the output buffer needs room for one at its end, as the VPCOMPRESSD page explains, or the store can be a VMOVDQU8 under a mask of the low n bits, which BZHI of an all-ones value gives. The cases recorded on Zen 5 agree with the page’s pseudocode for both forms: the memory form left the bytes above the packed ones as they were, and the register form with {z} cleared them.

In the optimization guide

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

Zen 4

Forms

Every encoding of VPCOMPRESSB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPCOMPRESSB m128 {k}, xmm VPCOMPRESSB_MEMu8_MASKmskw_XMMu8_AVX512EVEX.128.66.0F38.W0 63 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPCOMPRESSB xmm {k}{z}, xmm VPCOMPRESSB_XMMu8_MASKmskw_XMMu8_AVX512EVEX.128.66.0F38.W0 63 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPCOMPRESSB m256 {k}, ymm VPCOMPRESSB_MEMu8_MASKmskw_YMMu8_AVX512EVEX.256.66.0F38.W0 63 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPCOMPRESSB ymm {k}{z}, ymm VPCOMPRESSB_YMMu8_MASKmskw_YMMu8_AVX512EVEX.256.66.0F38.W0 63 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPCOMPRESSB m512 {k}, zmm VPCOMPRESSB_MEMu8_MASKmskw_ZMMu8_AVX512EVEX.512.66.0F38.W0 63 /rAVX10.1 or AVX512_VBMI2
VPCOMPRESSB zmm {k}{z}, zmm VPCOMPRESSB_ZMMu8_MASKmskw_ZMMu8_AVX512EVEX.512.66.0F38.W0 63 /rAVX10.1 or AVX512_VBMI2

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.
Modelm128 {k}, xmmno mask
m256 {k}, ymmno mask
m128 {k}, xmmwith a mask
m256 {k}, ymmwith a mask
xmm {k}{z}, xmmno maskxmm {k}{z}, xmmwith a mask, zeroingymm {k}{z}, ymmno maskymm {k}{z}, ymmwith a mask, zeroingm512 {k}, zmmno maskm512 {k}, zmmwith a maskzmm {k}{z}, zmmno maskzmm {k}{z}, zmmwith a mask, zeroing
Ice Lake10 / 1p510 / 1p53 / 1p53 / 1p53 / 1p53 / 1p510 / 1p510 / 1p53 / 1p53 / 1p5
Sapphire Rapids12 / 2p05614 / 2p0563 / 2p56 / 2p53 / 2p56 / 2p512 / 2p0 p1 p5 p6 p1114 / 2p0 p1 p5 p6 p113 / 2p56 / 2p5
Zen 48 / 0.5FP1 FP28 / 0.5FP1 FP22 / 1FP1 FP22 / 1FP1 FP24 / 1FP1 FP24 / 1FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP25 / 1FP1 FP25 / 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.

Compress to memory: the bytes whose bit of k1 is 1 are stored one after another from the lowest address; the rest of the memory operand is not written.Memory forms
VPCOMPRESSB with memory destinationMemory bytes 15 to 0: unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, a14, a13, a11, a8, a7, a5, a2, a1.1111111100000000k10346910121512578111314xmm2aa1a2a5a7a8a11a13a14m128

Example mask k1 = 0x69A6. Shown for the xmm form; the ymm and zmm forms work the same on 32 and 64 bytes.

Memory bytes 15 to 0: unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, a14, a13, a11, a8, a7, a5, a2, a1.

Compress: the bytes whose bit of k1 is 1 are packed together from byte 0 up; above them merging keeps the old elements, and zeroing writes 0.Register forms

merging, {k1}

VPCOMPRESSB with merging, {k1}With merging: result bytes 15 to 0: unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, a14, a13, a11, a8, a7, a5, a2, a1.xmm1

zeroing, {k1}{z}

VPCOMPRESSB with zeroing, {k1}{z}With zeroing: result bytes 15 to 0: 0, 0, 0, 0, 0, 0, 0, 0, a14, a13, a11, a8, a7, a5, a2, a1.00000000

Example mask k1 = 0x69A6. Shown for the xmm form; the ymm and zmm forms work the same on 32 and 64 bytes.

With merging: result bytes 15 to 0: unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, a14, a13, a11, a8, a7, a5, a2, a1.

With zeroing: result bytes 15 to 0: 0, 0, 0, 0, 0, 0, 0, 0, a14, a13, a11, a8, a7, a5, a2, a1.

Operation

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

Memory forms
j = 0
for i in range(VL // 8):
    if k1[i]:
        mem.b[j] = zmm2.b[i]
        j += 1
# the memory above element j is not written

Run on AMD Zen 5 (EPYC 9645): 3 cases.

Register forms
j = 0
for i in range(VL // 8):
    if k1[i]:
        zmm1.b[j] = zmm2.b[i]
        j += 1
if zeroing:
    for i in range(j, VL // 8):
        zmm1.b[i] = 0
# else: the elements from j up keep their values
# zmm1 is zeroed from bit VL up

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

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-E4

Attributes

What else XED records about the forms. How to read.

All forms
write masking
Memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPCOMPRESSB, 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_mask_compress_epi8 __m128i _mm_mask_compress_epi8(__m128i __S, __mmask16 __U, __m128i __D)

VPCOMPRESSB xmm {k}, xmm EVEX.128 -mavx512vl -mavx512vbmi2

_mm_mask_compressstoreu_epi8 void _mm_mask_compressstoreu_epi8(void *__P, __mmask16 __U, __m128i __D)

VPCOMPRESSB m128 {k}, xmm EVEX.128 -mavx512vl -mavx512vbmi2

_mm_maskz_compress_epi8 __m128i _mm_maskz_compress_epi8(__mmask16 __U, __m128i __D)

VPCOMPRESSB xmm {k}{z}, xmm EVEX.128 -mavx512vl -mavx512vbmi2

_mm256_mask_compress_epi8 __m256i _mm256_mask_compress_epi8(__m256i __S, __mmask32 __U, __m256i __D)

VPCOMPRESSB ymm {k}, ymm EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_mask_compressstoreu_epi8 void _mm256_mask_compressstoreu_epi8(void *__P, __mmask32 __U, __m256i __D)

VPCOMPRESSB m256 {k}, ymm EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_maskz_compress_epi8 __m256i _mm256_maskz_compress_epi8(__mmask32 __U, __m256i __D)

VPCOMPRESSB ymm {k}{z}, ymm EVEX.256 -mavx512vl -mavx512vbmi2

_mm512_mask_compress_epi8 __m512i _mm512_mask_compress_epi8(__m512i __S, __mmask64 __U, __m512i __D)

VPCOMPRESSB zmm {k}, zmm EVEX.512 -mavx512vbmi2

_mm512_mask_compressstoreu_epi8 void _mm512_mask_compressstoreu_epi8(void *__P, __mmask64 __U, __m512i __D)

VPCOMPRESSB m512 {k}, zmm EVEX.512 -mavx512vbmi2

_mm512_maskz_compress_epi8 __m512i _mm512_maskz_compress_epi8(__mmask64 __U, __m512i __D)

VPCOMPRESSB zmm {k}{z}, zmm EVEX.512 -mavx512vbmi2

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_VBMI2_128

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

or

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

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_VBMI2_256
Same as AVX512_VBMI2_128Same as AVX512_VBMI2_128
AVX512_VBMI2_512

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

or

AVX512_VBMI2
CPUID.(EAX=07H,ECX=0):ECX[6] AVX512_VBMI2

Same as AVX512_VBMI2_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-468 (VPCOMPRESSB/VCOMPRESSW)
  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.