Extensions
Forms
18 (6 VEX, 12 EVEX)
Data
Intel XED v2026.08.23

VPSLLD shifts each doubleword left by one shared count, filling with zeros: the VEX and EVEX form of PSLLD, whose page covers the operation, with the count rules PSLLW gives for the family. Even in the YMM and ZMM forms the count is an immediate or the low quadword of an XMM register or of memory, and any count above 31 clears the element. VEX.128 needs AVX and VEX.256 AVX2; the EVEX forms (AVX-512F) add masking, the 512-bit width and, in the immediate form only, a source read from memory, whole or as one broadcast doubleword. Every form writes a separate destination, zeroes it above the vector length and takes memory at any alignment.

On Zen 5, the recorded vpslld ymm0, ymm13, 0x10 shifted all eight doublewords alike, 7FFFFFFFh becoming FFFF0000h in either 128-bit lane; vpslld ymm7, ymm11, xmm7, with a count of 33, cleared all eight; and vpslld zmm9{k5}, dword bcst [mem], 3 wrote 0, from 80000000h, into the nine elements k5 selects and kept the other seven.

In compiled code

In our builds at -O2 over uint32_t arrays, b[i] << 3 is VPSLLD by 3 with -march=x86-64-v3 in GCC 14 and Clang 23; with -march=x86-64-v4 both shift straight from memory, which only EVEX can. For b[i] << n, GCC moves n into an XMM register for VPSLLD, while Clang broadcasts it for VPSLLVD. A rotate by 7 is VPSLLD, VPSRLD and VPOR at -v3, one VPROLD at -v4. c[i] ? b[i] << 3 : b[i] shifts and blends at -v3; at -v4 both mask the shift itself.

Intel’s optimization manual compares masking with blending on a VPSLLD and a VPSRLD: merge-masked into one register, they wait for each other, and computing both and merging once was faster (Section 17.2.3; see the guide). AMD’s latency spreadsheet for Zen 5 gives the EVEX immediate form one cycle on pipes FP2 and FP3 and the count from a register two cycles on FP0 and FP1, the figure its single row for the VEX forms gives them all.

Forms

Every encoding of VPSLLD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSLLD xmm, xmm, m128 VPSLLD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG F2 /rAVX
VPSLLD xmm, xmm, xmm VPSLLD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG F2 /rAVX
VPSLLD xmm, xmm, imm8 VPSLLD_XMMdq_XMMdq_IMMbVEX.128.66.0F.WIG 72 /6 ibAVX
VPSLLD ymm, ymm, m128 VPSLLD_YMMqq_YMMqq_MEMdqVEX.256.66.0F.WIG F2 /rAVX2
VPSLLD ymm, ymm, xmm VPSLLD_YMMqq_YMMqq_XMMqVEX.256.66.0F.WIG F2 /rAVX2
VPSLLD ymm, ymm, imm8 VPSLLD_YMMqq_YMMqq_IMMbVEX.256.66.0F.WIG 72 /6 ibAVX2
VPSLLD zmm {k}{z}, zmm, xmm VPSLLD_ZMMu32_MASKmskw_ZMMu32_XMMu32_AVX512EVEX.512.66.0F.W0 F2 /rAVX10.1 or AVX512F
VPSLLD zmm {k}{z}, zmm, m128 VPSLLD_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512EVEX.512.66.0F.W0 F2 /rAVX10.1 or AVX512F
VPSLLD zmm {k}{z}, zmm, imm8 VPSLLD_ZMMu32_MASKmskw_ZMMu32_IMM8_AVX512EVEX.512.66.0F.W0 72 /6 ibAVX10.1 or AVX512F
VPSLLD zmm {k}{z}, m512/m32bcst, imm8 VPSLLD_ZMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.512.66.0F.W0 72 /6 ibAVX10.1 or AVX512F
VPSLLD xmm {k}{z}, xmm, imm8 VPSLLD_XMMu32_MASKmskw_XMMu32_IMM8_AVX512EVEX.128.66.0F.W0 72 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLD xmm {k}{z}, m128/m32bcst, imm8 VPSLLD_XMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.128.66.0F.W0 72 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLD xmm {k}{z}, xmm, xmm VPSLLD_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512EVEX.128.66.0F.W0 F2 /rAVX10.1 or AVX512F + AVX512VL
VPSLLD xmm {k}{z}, xmm, m128 VPSLLD_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512EVEX.128.66.0F.W0 F2 /rAVX10.1 or AVX512F + AVX512VL
VPSLLD ymm {k}{z}, ymm, imm8 VPSLLD_YMMu32_MASKmskw_YMMu32_IMM8_AVX512EVEX.256.66.0F.W0 72 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLD ymm {k}{z}, m256/m32bcst, imm8 VPSLLD_YMMu32_MASKmskw_MEMu32_IMM8_AVX512EVEX.256.66.0F.W0 72 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLD ymm {k}{z}, ymm, xmm VPSLLD_YMMu32_MASKmskw_YMMu32_XMMu32_AVX512EVEX.256.66.0F.W0 F2 /rAVX10.1 or AVX512F + AVX512VL
VPSLLD ymm {k}{z}, ymm, m128 VPSLLD_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512EVEX.256.66.0F.W0 F2 /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.
Modelxmm, xmm, m128
xmm {k}{z}, xmm, m128
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
xmm, xmm, imm8ymm, ymm, m128
ymm {k}{z}, m256/m32bcst, imm8
ymm {k}{z}, ymm, m128
ymm, ymm, xmm
ymm {k}{z}, ymm, xmm
ymm, ymm, imm8zmm {k}{z}, zmm, xmmzmm {k}{z}, zmm, m128
zmm {k}{z}, m512/m32bcst, imm8
zmm {k}{z}, zmm, imm8xmm {k}{z}, xmm, imm8
ymm {k}{z}, ymm, imm8
xmm {k}{z}, m128/m32bcst, imm8
Sandy Bridge8 / 1p0152 / 1p0151 / 1p0
Haswell8 / 1p02 / 1p051 / 1p08 / 1p04 / 1p051 / 1p0
Broadwell7 / 1p02 / 1p051 / 1p07 / 1p04 / 1p051 / 1p0
Skylake7 / 0.5p012 / 1p0151 / 0.5p018 / 0.5p014 / 1p0151 / 0.5p01
Skylake-SP7 / 0.5p012 / 1p0151 / 0.5p018 / 0.5p014 / 1p0151 / 0.5p014 / 1p058 / 1p01 / 1p01 / 0.5p017 / 0.5p01
Ice Lake7 / 0.5p012 / 0.67p0151 / 0.5p018 / 0.5p014 / 1p0151 / 0.5p014 / 1p058 / 1p01 / 1p01 / 0.5p017 / 0.5p01
Alder Lake8 / 0.5p012 / 0.67p0151 / 0.5p019 / 0.5p014 / 1p0151 / 0.5p01
Sapphire Rapids8 / 0.5p012 / 0.67p0151 / 0.5p019 / 0.5p014 / 1p0151 / 0.5p014 / 1p059 / 1p01 / 1p01 / 0.5p018 / 0.5p01
Lunar Lake8 / 0.5V0 V12 / 0.5V0 V1 V2 V31 / 0.5V0 V19 / 2.33V0 V14 / 0.5V0 V1 V2 V31 / 0.5V0 V1
Piledriver8 / 1.5FPU1 FPXBR3 / 1FPU1 FPXBR2 / 1FPU1 FPXBR
Zen8 / 1FPU21 / 1FPU21 / 1FPU28 / 2FPU21 / 2FPU21 / 2FPU2
Zen 28 / 1FPU21 / 1FPU21 / 1FPU28 / 1FPU21 / 1FPU21 / 1FPU2
Zen 38 / 0.5FP1 FP21 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP21 / 0.5FP1 FP2
Zen 49 / 1FP1 FP22 / 11FP0 FP11 / 0.5FP1 FP28 / 0.5FP1 FP22 / 12FP0 FP11 / 0.5FP1 FP22 / 1FP0 FP18 / 1FP1 FP21 / 0.5FP0 FP11 / 0.5FP0 FP18 / 0.5FP1 FP2
Jaguar7 / 1FPU0 FPU1 VALU0 VALU12 / 0.5FPU0 FPU1 VALU0 VALU12 / 0.5FPU0 FPU1 VALU0 VALU1
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2904; AMD 58455, row 1168).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2908; AMD 58455, row 1168).

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.

Element-wise, by one count: each doubleword is shifted by the count in the low 64 bits of xmm3.VPSLLD xmm, xmm, xmm/m128 VPSLLD ymm, ymm, xmm/m128 VPSLLD xmm {k}{z}, xmm, xmm/m128 VPSLLD ymm {k}{z}, ymm, xmm/m128 VPSLLD zmm {k}{z}, zmm, xmm/m128
VPSLLD: element by elementResult doubleword i comes from doubleword i of xmm2 and the count in xmm3. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2a1110k1r0r1r3xmm1countxmm3or m128c

Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result doubleword i comes from doubleword i of xmm2 and the count in xmm3. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.

Element-wise: each doubleword of the result comes from the doubleword in the same place in each source.VPSLLD xmm, xmm, imm8 VPSLLD ymm, ymm, imm8 VPSLLD xmm {k}{z}, xmm/m128/m32bcst, imm8 VPSLLD ymm {k}{z}, ymm/m256/m32bcst, imm8 VPSLLD zmm {k}{z}, zmm/m512/m32bcst, imm8
VPSLLD: element by elementResult doubleword i comes from doubleword i of xmm2. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.xmm2or m128a

Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m32bcst, one doubleword from memory stands for every element of the last source.

Result doubleword i comes from doubleword i of xmm2. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.

Operation

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

VPSLLD xmm, xmm, xmm/m128 VPSLLD ymm, ymm, xmm/m128 VPSLLD xmm {k}{z}, xmm, xmm/m128 VPSLLD ymm {k}{z}, ymm, xmm/m128 VPSLLD zmm {k}{z}, zmm, xmm/m128
count = src3.q[0]
for i in range(VL // 32):
    if k1[i]:  # 1 without a write mask
        a = zmm2.d[i]
        if count < 32:
            zmm1.d[i] = a << count
        else:
            zmm1.d[i] = 0
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# zmm1 is zeroed from bit VL up

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

VPSLLD xmm, xmm, imm8 VPSLLD ymm, ymm, imm8 VPSLLD xmm {k}{z}, xmm/m128/m32bcst, imm8 VPSLLD ymm {k}{z}, ymm/m256/m32bcst, imm8 VPSLLD zmm {k}{z}, zmm/m512/m32bcst, imm8
for i in range(VL // 32):
    if k1[i]:  # 1 without a write mask
        a = src2.d[i]
        if imm8 < 32:
            zmm1.d[i] = a << imm8
        else:
            zmm1.d[i] = 0
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src2.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 8 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
VPSLLD xmm, xmm, xmm/m128 VPSLLD ymm, ymm, xmm/m128
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128explicitread
VPSLLD xmm, xmm, imm8 VPSLLD ymm, ymm, imm8
xmm, ymmexplicitwrite
xmm, ymmexplicitread
imm8explicitread
VPSLLD xmm {k}{z}, xmm, xmm/m128 VPSLLD ymm {k}{z}, ymm, xmm/m128 VPSLLD zmm {k}{z}, zmm, xmm/m128
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128explicitread
VPSLLD xmm {k}{z}, xmm/m128/m32bcst, imm8 VPSLLD ymm {k}{z}, ymm/m256/m32bcst, imm8 VPSLLD zmm {k}{z}, zmm/m512/m32bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread
imm8explicitread

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.

VPSLLD xmm, xmm, xmm/m128 VPSLLD xmm, xmm, imm8 VPSLLD ymm, ymm, imm8
avx-type-7
VPSLLD ymm, ymm, xmm/m128
avx-type-4
VPSLLD xmm {k}{z}, xmm, xmm/m128 VPSLLD ymm {k}{z}, ymm, xmm/m128 VPSLLD zmm {k}{z}, zmm, xmm/m128
AVX512-E4NF
VPSLLD xmm {k}{z}, xmm/m128/m32bcst, imm8 VPSLLD ymm {k}{z}, ymm/m256/m32bcst, imm8 VPSLLD zmm {k}{z}, zmm/m512/m32bcst, imm8
AVX512-E4

Attributes

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

EVEX forms
write masking
VPSLLD xmm {k}{z}, m128/m32bcst, imm8 VPSLLD ymm {k}{z}, m256/m32bcst, imm8 VPSLLD zmm {k}{z}, m512/m32bcst, imm8
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSLLD, 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_sll_epi32 __m128i _mm_sll_epi32(__m128i __a, __m128i __count)

VPSLLD xmm, xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_slli_epi32 __m128i _mm_slli_epi32(__m128i __a, int __count)

VPSLLD xmm, xmm, imm8 VEX.128 -mavxwith AVX enabled; with __count a constant

_mm_mask_sll_epi32 __m128i _mm_mask_sll_epi32(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B)

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

_mm_mask_slli_epi32 __m128i _mm_mask_slli_epi32(__m128i __W, __mmask8 __U, __m128i __A, unsigned int __B)

VPSLLD xmm {k}, xmm, imm8 EVEX.128 -mavx512vlwith __B a constant

_mm_maskz_sll_epi32 __m128i _mm_maskz_sll_epi32(__mmask8 __U, __m128i __A, __m128i __B)

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

_mm_maskz_slli_epi32 __m128i _mm_maskz_slli_epi32(__mmask8 __U, __m128i __A, unsigned int __B)

VPSLLD xmm {k}{z}, xmm, imm8 EVEX.128 -mavx512vlwith __B a constant

_mm256_sll_epi32 __m256i _mm256_sll_epi32(__m256i __a, __m128i __count)

VPSLLD ymm, ymm, xmm VEX.256 -mavx2

_mm256_slli_epi32 __m256i _mm256_slli_epi32(__m256i __a, int __count)

VPSLLD ymm, ymm, imm8 VEX.256 -mavx2with __count a constant

_mm256_mask_sll_epi32 __m256i _mm256_mask_sll_epi32(__m256i __W, __mmask8 __U, __m256i __A, __m128i __B)

VPSLLD ymm {k}, ymm, xmm EVEX.256 -mavx512vl

_mm256_mask_slli_epi32 __m256i _mm256_mask_slli_epi32(__m256i __W, __mmask8 __U, __m256i __A, unsigned int __B)

VPSLLD ymm {k}, ymm, imm8 EVEX.256 -mavx512vlwith __B a constant

_mm256_maskz_sll_epi32 __m256i _mm256_maskz_sll_epi32(__mmask8 __U, __m256i __A, __m128i __B)

VPSLLD ymm {k}{z}, ymm, xmm EVEX.256 -mavx512vl

_mm256_maskz_slli_epi32 __m256i _mm256_maskz_slli_epi32(__mmask8 __U, __m256i __A, unsigned int __B)

VPSLLD ymm {k}{z}, ymm, imm8 EVEX.256 -mavx512vlwith __B a constant

_mm512_sll_epi32 __m512i _mm512_sll_epi32(__m512i __A, __m128i __B)

VPSLLD zmm, zmm, xmm EVEX.512 -mavx512f

_mm512_slli_epi32 __m512i _mm512_slli_epi32(__m512i __A, unsigned int __B)

VPSLLD zmm, zmm, imm8 EVEX.512 -mavx512fwith __B a constant

_mm512_mask_sll_epi32 __m512i _mm512_mask_sll_epi32(__m512i __W, __mmask16 __U, __m512i __A, __m128i __B)

VPSLLD zmm {k}, zmm, xmm EVEX.512 -mavx512f

_mm512_mask_slli_epi32 __m512i _mm512_mask_slli_epi32(__m512i __W, __mmask16 __U, __m512i __A, unsigned int __B)

VPSLLD zmm {k}, zmm, imm8 EVEX.512 -mavx512fwith __B a constant

_mm512_maskz_sll_epi32 __m512i _mm512_maskz_sll_epi32(__mmask16 __U, __m512i __A, __m128i __B)

VPSLLD zmm {k}{z}, zmm, xmm EVEX.512 -mavx512f

_mm512_maskz_slli_epi32 __m512i _mm512_maskz_slli_epi32(__mmask16 __U, __m512i __A, unsigned int __B)

VPSLLD zmm {k}{z}, zmm, imm8 EVEX.512 -mavx512fwith __B a constant

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
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX2

AVX2
CPUID.(EAX=07H,ECX=0):EBX[5] AVX2

Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
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 AVX instructions

All 253 AVX instructions

More AVX2 instructions

All 138 AVX2 instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-443 (PSLLW/PSLLD/PSLLQ)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  9. 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.