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

VPSCATTERDD stores the doublewords of a vector to scattered addresses: element i goes to a base plus element i of an index vector, a signed 32-bit integer, times a scale of 1, 2, 4 or 8. It is d[idx[i]] = s[i] in one instruction, the store that mirrors VPGATHERDD. Scatters exist only in AVX-512; AVX2 has gathers but no scatter. As with the gathers (see VGATHERDPS), a mask register chooses the elements, each mask bit is cleared as its element is stored, and the whole mask register is zero at the end; a fault partway leaves the elements below the faulting one stored and their bits cleared, so that the instruction can resume.

Repeated indices

Two elements may name the same address. Intel’s manual guarantees that overlapping stores happen in element order, so the highest element wins, and lets the processor skip the earlier stores to an address written again. Stores that do not overlap may happen in any order. In a case recorded on Zen 5 whose 16 indices took only two values, memory kept the values of elements 13 and 15, the last ones with each index.

That order is what lets compilers vectorize a plain scatter loop: in d[idx[i]] = s[i] the scalar loop’s last write wins too. GCC 14 and Clang 23 at -O2 turn it into VPSCATTERDD for -march=x86-64-v4, with an all-ones mask made by KXNORW or KXNORB; for znver4 and znver5 Clang uses zmm registers, and GCC keeps the loop scalar. A read-modify-write such as a histogram, h[idx[i]] += 1, is different: a gather, an addition and a scatter lose the counts of repeated indices, which is the problem VPCONFLICTD solves.

Cost

A scatter is one store per element. Intel’s optimization guide warns against using it for sequential elements, which one vector store writes, and in its example of a conversion followed by a scatter, measures the hardware scatter only slightly ahead of a software sequence of permutes and scalar stores, 1.53 against 1.48 times scalar code (Section 17.11.1, Table 17-4). AMD’s Zen 5 guide lists every scatter as microcoded.

VPSCATTERQD takes 64-bit indices, VPSCATTERDQ and VPSCATTERQQ store quadwords, and VSCATTERDPS singles.

In the optimization guide

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

Vectors

  • Gathers and scatters: Scatters store one element at a time; Intel replaces short-stride scatters by permutes and stores, and they are microcode on Zen 5.

Forms

Every encoding of VPSCATTERDD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSCATTERDD vm32z {k}, zmm VPSCATTERDD_MEMu32_MASKmskw_ZMMu32_AVX512_VL512EVEX.512.66.0F38.W0 A0 /rAVX10.1 or AVX512F
VPSCATTERDD vm32x {k}, xmm VPSCATTERDD_MEMu32_MASKmskw_XMMu32_AVX512_VL128EVEX.128.66.0F38.W0 A0 /rAVX10.1 or AVX512F + AVX512VL
VPSCATTERDD vm32y {k}, ymm VPSCATTERDD_MEMu32_MASKmskw_YMMu32_AVX512_VL256EVEX.256.66.0F38.W0 A0 /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.
Modelvm32z {k}, zmmvm32x {k}, xmmvm32y {k}, ymm
Skylake-SP8 / 16p01568 / 4p01568 / 8p0156
Ice Lake8 / 8p01568 / 2p01568 / 4p0156
Sapphire Rapids19 / 8p0 p1 p5 p6 p1112 / 2p0 p1 p5 p6 p1112 / 4p0 p1 p5 p6 p11
Zen 41 / 1AGU0 AGU1 AGU2 LSU Store1 / 1AGU0 AGU1 AGU2 LSU Store1 / 1AGU0 AGU1 AGU2 LSU Store

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.

Scatter: doubleword i of ymm2 is stored at base + index i × scale, where its mask bit is 1; when two indices are equal, the higher element is stored.
VPSCATTERDD with example indicesWith the example indices, memory elements 15 to 0: unchanged, a6, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, a4, unchanged, a3, unchanged, a7, a1, unchanged, a5.5211570143vm32yindex11111110k101345672ymm2aa5a1a7a3a4a6memory

Example: indices 3, 14, 0, 7, 5, 11, 2, 5 from element 7 down, mask k1 = 0xFB; memory elements are numbered from the base address in units of the scale. The other forms scatter 4 and 16 elements, one for each index. The mask is cleared as the elements complete.

With the example indices, memory elements 15 to 0: unchanged, a6, unchanged, unchanged, unchanged, unchanged, unchanged, unchanged, a4, unchanged, a3, unchanged, a7, a1, unchanged, a5.

Operation

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

for i in range(VL // 32):
    if k1[i]:
        a = mem.index.sd[i] * mem.scale
        store(mem.base + a, 32, zmm2.d[i])
k1.write(0)  # all of it

Run on AMD Zen 5 (EPYC 9645): 15 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
VPSCATTERDD vm32x {k}, xmm VPSCATTERDD vm32y {k}, ymm VPSCATTERDD vm32z {k}, zmm
vm32x, vm32y, vm32zexplicitwrite (masked)
{k}explicitread, write (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-E12

Attributes

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

All forms
scatter; write masking; memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSCATTERDD, 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_i32scatter_epi32 void _mm_i32scatter_epi32(void *addr, __m128i index, __m128i v1, const int scale)

VPSCATTERDD vm32x {k}, xmm EVEX.128 -mavx512vl

_mm_mask_i32scatter_epi32 void _mm_mask_i32scatter_epi32(void *addr, __mmask8 mask, __m128i index, __m128i v1, const int scale)

VPSCATTERDD vm32x {k}, xmm EVEX.128 -mavx512vl

_mm256_i32scatter_epi32 void _mm256_i32scatter_epi32(void *addr, __m256i index, __m256i v1, const int scale)

VPSCATTERDD vm32y {k}, ymm EVEX.256 -mavx512vl

_mm256_mask_i32scatter_epi32 void _mm256_mask_i32scatter_epi32(void *addr, __mmask8 mask, __m256i index, __m256i v1, const int scale)

VPSCATTERDD vm32y {k}, ymm EVEX.256 -mavx512vl

_mm512_i32scatter_epi32 void _mm512_i32scatter_epi32(void *addr, __m512i index, __m512i v1, const int scale)

VPSCATTERDD vm32z {k}, zmm EVEX.512 -mavx512f

_mm512_mask_i32scatter_epi32 void _mm512_mask_i32scatter_epi32(void *addr, __mmask16 mask, __m512i index, __m512i v1, const int scale)

VPSCATTERDD vm32z {k}, 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-618 (VPSCATTERDD/VPSCATTERDQ/VPSCATTERQD/VPSCATTERQQ)
  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.