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

VPSLLQ shifts each quadword left by one shared count, filling with zeros: the VEX and EVEX form of PSLLQ, whose page covers the operation and why bits never cross from one quadword to the next. The forms are those of VPSLLD: three operands, VEX.128 for AVX and VEX.256 for AVX2, EVEX (AVX-512F) with masking, the 512-bit width and a memory source for the immediate form, here whole or as one broadcast quadword. The count is an immediate or the low quadword of an XMM register or of memory, and anything above 63 clears the element.

Zen 5’s recorded cases: vpsllq ymm1, ymm2, xmm3 took its count, 3, from the low quadword of XMM3 and ignored the random bits above it, turning FFFFFFFFFFFFFFFFh into FFFFFFFFFFFFFFF8h in both lanes; {evex} vpsllq ymm9, ymm9, [mem], whose count was 8000000000000000h, cleared all four quadwords; and vpsllq zmm0{k5}, qword bcst [mem], 0xff cleared the four elements k5 selects and kept the other four.

In compiled code

In our builds at -O2 over uint64_t arrays, b[i] << 3 is VPSLLQ by 3 with -march=x86-64-v3 in GCC 14 and Clang 23, read straight from memory with -march=x86-64-v4. AVX2 has no 64-bit multiply, and b[i] * c[i] at -v3 is built from 32-bit products in both compilers: two VPSRLQ by 32 bring the high halves down, three VPMULUDQ form the partial products, and VPSLLQ by 32 moves the sum of the cross products up before the last VPADDQ. At -v4 it is one VPMULLQ, from AVX512DQ.

Intel’s optimization manual names VPSLLQ with VPMULUDQ, VPADDQ, VPSRLQ, VPBROADCASTQ and VPERMQ as the AVX2 instructions for vectorized modular multiplication, with numbers held as 29-bit digits in doublewords so that the 64-bit products leave room for carries (Section 15.16.2). 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 one row for the VEX forms gives them all.

Forms

Every encoding of VPSLLQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSLLQ xmm, xmm, m128 VPSLLQ_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG F3 /rAVX
VPSLLQ xmm, xmm, xmm VPSLLQ_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG F3 /rAVX
VPSLLQ xmm, xmm, imm8 VPSLLQ_XMMdq_XMMdq_IMMbVEX.128.66.0F.WIG 73 /6 ibAVX
VPSLLQ ymm, ymm, m128 VPSLLQ_YMMqq_YMMqq_MEMdqVEX.256.66.0F.WIG F3 /rAVX2
VPSLLQ ymm, ymm, xmm VPSLLQ_YMMqq_YMMqq_XMMqVEX.256.66.0F.WIG F3 /rAVX2
VPSLLQ ymm, ymm, imm8 VPSLLQ_YMMqq_YMMqq_IMMbVEX.256.66.0F.WIG 73 /6 ibAVX2
VPSLLQ zmm {k}{z}, zmm, xmm VPSLLQ_ZMMu64_MASKmskw_ZMMu64_XMMu64_AVX512EVEX.512.66.0F.W1 F3 /rAVX10.1 or AVX512F
VPSLLQ zmm {k}{z}, zmm, m128 VPSLLQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F.W1 F3 /rAVX10.1 or AVX512F
VPSLLQ zmm {k}{z}, zmm, imm8 VPSLLQ_ZMMu64_MASKmskw_ZMMu64_IMM8_AVX512EVEX.512.66.0F.W1 73 /6 ibAVX10.1 or AVX512F
VPSLLQ zmm {k}{z}, m512/m64bcst, imm8 VPSLLQ_ZMMu64_MASKmskw_MEMu64_IMM8_AVX512EVEX.512.66.0F.W1 73 /6 ibAVX10.1 or AVX512F
VPSLLQ xmm {k}{z}, xmm, imm8 VPSLLQ_XMMu64_MASKmskw_XMMu64_IMM8_AVX512EVEX.128.66.0F.W1 73 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLQ xmm {k}{z}, m128/m64bcst, imm8 VPSLLQ_XMMu64_MASKmskw_MEMu64_IMM8_AVX512EVEX.128.66.0F.W1 73 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLQ xmm {k}{z}, xmm, xmm VPSLLQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F.W1 F3 /rAVX10.1 or AVX512F + AVX512VL
VPSLLQ xmm {k}{z}, xmm, m128 VPSLLQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F.W1 F3 /rAVX10.1 or AVX512F + AVX512VL
VPSLLQ ymm {k}{z}, ymm, imm8 VPSLLQ_YMMu64_MASKmskw_YMMu64_IMM8_AVX512EVEX.256.66.0F.W1 73 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLQ ymm {k}{z}, m256/m64bcst, imm8 VPSLLQ_YMMu64_MASKmskw_MEMu64_IMM8_AVX512EVEX.256.66.0F.W1 73 /6 ibAVX10.1 or AVX512F + AVX512VL
VPSLLQ ymm {k}{z}, ymm, xmm VPSLLQ_YMMu64_MASKmskw_YMMu64_XMMu64_AVX512EVEX.256.66.0F.W1 F3 /rAVX10.1 or AVX512F + AVX512VL
VPSLLQ ymm {k}{z}, ymm, m128 VPSLLQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F.W1 F3 /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/m64bcst, 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/m64bcst, imm8
zmm {k}{z}, zmm, imm8xmm {k}{z}, xmm, imm8
ymm {k}{z}, ymm, imm8
xmm {k}{z}, m128/m64bcst, 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 2915; AMD 58455, row 1171).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2919; AMD 58455, row 1171).

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 quadword is shifted by the count in the low 64 bits of xmm3.VPSLLQ xmm, xmm, xmm/m128 VPSLLQ ymm, ymm, xmm/m128 VPSLLQ xmm {k}{z}, xmm, xmm/m128 VPSLLQ ymm {k}{z}, ymm, xmm/m128 VPSLLQ zmm {k}{z}, zmm, xmm/m128
VPSLLQ: element by elementResult quadword i comes from quadword i of xmm2 and the count in xmm3. Result quadwords 1 to 0: r1, r0.01xmm2a11k1r0r1xmm1countxmm3or m128c

Every quadword works alike: 2, 4 and 8 quadwords 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 quadword i comes from quadword i of xmm2 and the count in xmm3. Result quadwords 1 to 0: r1, r0.

Element-wise: each quadword of the result comes from the quadword in the same place in each source.VPSLLQ xmm, xmm, imm8 VPSLLQ ymm, ymm, imm8 VPSLLQ xmm {k}{z}, xmm/m128/m64bcst, imm8 VPSLLQ ymm {k}{z}, ymm/m256/m64bcst, imm8 VPSLLQ zmm {k}{z}, zmm/m512/m64bcst, imm8
VPSLLQ: element by elementResult quadword i comes from quadword i of xmm2. Result quadwords 1 to 0: r1, r0.xmm2or m128a

Every quadword works alike: 2, 4 and 8 quadwords 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 m64bcst, one quadword from memory stands for every element of the last source.

Result quadword i comes from quadword i of xmm2. Result quadwords 1 to 0: r1, r0.

Operation

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

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

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

VPSLLQ xmm, xmm, imm8 VPSLLQ ymm, ymm, imm8 VPSLLQ xmm {k}{z}, xmm/m128/m64bcst, imm8 VPSLLQ ymm {k}{z}, ymm/m256/m64bcst, imm8 VPSLLQ zmm {k}{z}, zmm/m512/m64bcst, imm8
for i in range(VL // 64):
    if k1[i]:  # 1 without a write mask
        a = src2.q[i]
        if imm8 < 64:
            zmm1.q[i] = a << imm8
        else:
            zmm1.q[i] = 0
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src2.q[i] is the m64 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
VPSLLQ xmm, xmm, xmm/m128 VPSLLQ ymm, ymm, xmm/m128
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128explicitread
VPSLLQ xmm, xmm, imm8 VPSLLQ ymm, ymm, imm8
xmm, ymmexplicitwrite
xmm, ymmexplicitread
imm8explicitread
VPSLLQ xmm {k}{z}, xmm, xmm/m128 VPSLLQ ymm {k}{z}, ymm, xmm/m128 VPSLLQ zmm {k}{z}, zmm, xmm/m128
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128explicitread
VPSLLQ xmm {k}{z}, xmm/m128/m64bcst, imm8 VPSLLQ ymm {k}{z}, ymm/m256/m64bcst, imm8 VPSLLQ zmm {k}{z}, zmm/m512/m64bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread
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.

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

Attributes

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

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

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSLLQ, 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_epi64 __m128i _mm_sll_epi64(__m128i __a, __m128i __count)

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

_mm_slli_epi64 __m128i _mm_slli_epi64(__m128i __a, int __count)

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

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

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

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

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

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

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

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

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

_mm256_sll_epi64 __m256i _mm256_sll_epi64(__m256i __a, __m128i __count)

VPSLLQ ymm, ymm, xmm VEX.256 -mavx2

_mm256_slli_epi64 __m256i _mm256_slli_epi64(__m256i __a, int __count)

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

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

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

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

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

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

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

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

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

_mm512_sll_epi64 __m512i _mm512_sll_epi64(__m512i __A, __m128i __B)

VPSLLQ zmm, zmm, xmm EVEX.512 -mavx512f

_mm512_slli_epi64 __m512i _mm512_slli_epi64(__m512i __A, unsigned int __B)

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

_mm512_mask_sll_epi64 __m512i _mm512_mask_sll_epi64(__m512i __W, __mmask8 __U, __m512i __A, __m128i __B)

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

_mm512_mask_slli_epi64 __m512i _mm512_mask_slli_epi64(__m512i __W, __mmask8 __U, __m512i __A, unsigned int __B)

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

_mm512_maskz_sll_epi64 __m512i _mm512_maskz_sll_epi64(__mmask8 __U, __m512i __A, __m128i __B)

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

_mm512_maskz_slli_epi64 __m512i _mm512_maskz_slli_epi64(__mmask8 __U, __m512i __A, unsigned int __B)

VPSLLQ 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.