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

VCOMPRESSPD packs the doubles that a mask selects at the low end of its destination, in their original order: 2, 4 or 8 at a time, so the mask of a full ZMM register fits in a byte. It is VPCOMPRESSQ under a floating-point name, and VPCOMPRESSD’s page explains left-packing and the register and memory destinations; VCOMPRESSPS packs singles. The bits are moved as they are. It came with AVX512F.

Recorded on Zen 5

  • To memory. vcompresspd zmmword ptr [mem]{k2}, zmm0, with C9h in the low byte of K2, wrote elements 0, 3, 6 and 7 to the first 32 bytes and left the other 32 as they were.
  • Nothing selected. The XMM memory form with the low two bits of K6 clear wrote nothing.
  • Merging. vcompresspd zmm7{k6}, zmm12, with A4h in the low byte of K6, packed elements 2, 5 and 7 into elements 0 to 2 and kept the other five of ZMM7; the XMM form with both bits of K7 set copied the source and cleared the register above bit 127.
  • Zeroing. vcompresspd ymm14{k7}{z}, ymm8, with bits 0 and 1 of the four set, kept two elements and cleared the rest.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 keep the loop if (pd[i] > 0) po[n++] = pd[i]; over doubles scalar. VCOMPRESSPD comes from the intrinsics: _mm512_maskz_compress_pd is the zeroing register form, after a KMOVB of the mask in GCC and a KMOVD in Clang.

AMD’s Zen 5 latency spreadsheet gives the register forms two macro-ops on pipes FP1 and FP2, with 2, 4 and 5 cycles for XMM, YMM and ZMM, and lists the memory form as microcoded.

In the optimization guide

What the optimization guide says about VCOMPRESSPD, 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 VCOMPRESSPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCOMPRESSPD m512 {k}, zmm VCOMPRESSPD_MEMf64_MASKmskw_ZMMf64_AVX512EVEX.512.66.0F38.W1 8A /rAVX10.1 or AVX512F
VCOMPRESSPD zmm {k}{z}, zmm VCOMPRESSPD_ZMMf64_MASKmskw_ZMMf64_AVX512EVEX.512.66.0F38.W1 8A /rAVX10.1 or AVX512F
VCOMPRESSPD m128 {k}, xmm VCOMPRESSPD_MEMf64_MASKmskw_XMMf64_AVX512EVEX.128.66.0F38.W1 8A /rAVX10.1 or AVX512F + AVX512VL
VCOMPRESSPD xmm {k}{z}, xmm VCOMPRESSPD_XMMf64_MASKmskw_XMMf64_AVX512EVEX.128.66.0F38.W1 8A /rAVX10.1 or AVX512F + AVX512VL
VCOMPRESSPD m256 {k}, ymm VCOMPRESSPD_MEMf64_MASKmskw_YMMf64_AVX512EVEX.256.66.0F38.W1 8A /rAVX10.1 or AVX512F + AVX512VL
VCOMPRESSPD ymm {k}{z}, ymm VCOMPRESSPD_YMMf64_MASKmskw_YMMf64_AVX512EVEX.256.66.0F38.W1 8A /rAVX10.1 or AVX512F + AVX512VL

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.
Modelm512 {k}, zmmno mask
m128 {k}, xmmno mask
m256 {k}, ymmno mask
m512 {k}, zmmwith a mask
m128 {k}, xmmwith a mask
m256 {k}, ymmwith a mask
zmm {k}{z}, zmmno maskzmm {k}{z}, zmmwith a mask, zeroingxmm {k}{z}, xmmno maskxmm {k}{z}, xmmwith a mask, zeroingymm {k}{z}, ymmno maskymm {k}{z}, ymmwith a mask, zeroing
Skylake-SP, Ice Lake7 / 2p57 / 2p56 / 2p56 / 2p56 / 2p56 / 2p56 / 2p56 / 2p5
Sapphire Rapids12 / 2p515 / 2p53 / 2p56 / 2p53 / 2p56 / 2p53 / 2p56 / 2p5
Zen 48 / 0.5FP1 FP28 / 0.5FP1 FP25 / 1FP1 FP25 / 1FP1 FP22 / 1FP1 FP22 / 1FP1 FP24 / 1FP1 FP24 / 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 doubles 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
VCOMPRESSPD with memory destinationMemory doubles 7 to 0: unchanged, unchanged, unchanged, unchanged, a7, a5, a2, a1.11110000k103461257zmm2aa1a2a5a7m512

Example mask k1 = 0xA6. Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 doubles.

Memory doubles 7 to 0: unchanged, unchanged, unchanged, unchanged, a7, a5, a2, a1.

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

merging, {k1}

VCOMPRESSPD with merging, {k1}With merging: result doubles 7 to 0: unchanged, unchanged, unchanged, unchanged, a7, a5, a2, a1.zmm1

zeroing, {k1}{z}

VCOMPRESSPD with zeroing, {k1}{z}With zeroing: result doubles 7 to 0: 0, 0, 0, 0, a7, a5, a2, a1.0000

Example mask k1 = 0xA6. Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 doubles.

With merging: result doubles 7 to 0: unchanged, unchanged, unchanged, unchanged, a7, a5, a2, a1.

With zeroing: result doubles 7 to 0: 0, 0, 0, 0, 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 // 64):
    if k1[i]:
        mem.q[j] = zmm2.q[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 // 64):
    if k1[i]:
        zmm1.q[j] = zmm2.q[i]
        j += 1
if zeroing:
    for i in range(j, VL // 64):
        zmm1.q[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
VCOMPRESSPD xmm/m128 {k}{z}, xmm VCOMPRESSPD ymm/m256 {k}{z}, ymm VCOMPRESSPD 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 VCOMPRESSPD, 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_pd __m128d _mm_mask_compress_pd(__m128d __W, __mmask8 __U, __m128d __A)

VCOMPRESSPD xmm {k}, xmm EVEX.128 -mavx512vl

_mm_mask_compressstoreu_pd void _mm_mask_compressstoreu_pd(void *__P, __mmask8 __U, __m128d __A)

VCOMPRESSPD m128 {k}, xmm EVEX.128 -mavx512vl

_mm_maskz_compress_pd __m128d _mm_maskz_compress_pd(__mmask8 __U, __m128d __A)

VCOMPRESSPD xmm {k}{z}, xmm EVEX.128 -mavx512vl

_mm256_mask_compress_pd __m256d _mm256_mask_compress_pd(__m256d __W, __mmask8 __U, __m256d __A)

VCOMPRESSPD ymm {k}, ymm EVEX.256 -mavx512vl

_mm256_mask_compressstoreu_pd void _mm256_mask_compressstoreu_pd(void *__P, __mmask8 __U, __m256d __A)

VCOMPRESSPD m256 {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_compress_pd __m256d _mm256_maskz_compress_pd(__mmask8 __U, __m256d __A)

VCOMPRESSPD ymm {k}{z}, ymm EVEX.256 -mavx512vl

_mm512_mask_compress_pd __m512d _mm512_mask_compress_pd(__m512d __W, __mmask8 __U, __m512d __A)

VCOMPRESSPD zmm {k}, zmm EVEX.512 -mavx512f

_mm512_mask_compressstoreu_pd void _mm512_mask_compressstoreu_pd(void *__P, __mmask8 __U, __m512d __A)

VCOMPRESSPD m512 {k}, zmm EVEX.512 -mavx512f

_mm512_maskz_compress_pd __m512d _mm512_maskz_compress_pd(__mmask8 __U, __m512d __A)

VCOMPRESSPD zmm {k}{z}, zmm EVEX.512 -mavx512f

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
AVX512F_512

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

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] 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
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
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
AVX512F_256
Same as AVX512F_128Same as AVX512F_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-26 (VCOMPRESSPD)
  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.