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

VPSHLDD is a funnel shift per doubleword: it joins each element of the first source above the matching element of the second, shifts the 64-bit pair left by the immediate, taken modulo 32, and keeps the upper 32 bits. The bits shifted out of the first source are replaced by the top bits of the second, as SHLD does for general-purpose registers. VPSHRDD is the right-shifting counterpart, and VPSHLDVD takes per-element counts from a register.

It belongs to AVX512_VBMI2, which x86-64-v4 does not include: GCC 14 and Clang 23 need -mavx512vbmi2 (or a -march that has it) before they emit it.

Uses

  • Rotates of words. With the same register in both sources a funnel shift is a rotate. AVX-512F rotates doublewords and quadwords with VPROLD, but has no word rotate; Clang 23 at -O2 compiles (a << 3) | (a >> 13) on uint16_t vectors to vpshldw zmm0, zmm0, zmm0, 3, while GCC 14 keeps two shifts and an OR.
  • Shifting a long bit string. To shift a whole register, or an array, by a few bits, each element needs the top bits of its lower neighbour. VALIGND lines the neighbours up and VPSHLDD merges them: Clang vectorizes d[i] = (a[i+1] << 5) | (a[i] >> 27) that way, and with intrinsics both compilers shift a 512-bit register left by 5 bits as a zeroed register, a VALIGND and a VPSHLDD.
  • Combining shifted fields from two registers, the pattern (a << n) | (b >> (32 - n)), which Clang recognizes and emits as one VPSHLDD; GCC emits it only for the intrinsic.

AMD’s Zen 5 guide lists VPSHLDD and its word and right-shift kin as one macro-op with a latency of 2 cycles, the same as VPROLD. VPSHLDQ and VPSHLDW work on quadwords and words.

Forms

Every encoding of VPSHLDD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSHLDD xmm {k}{z}, xmm, xmm, imm8 VPSHLDD_XMMu32_MASKmskw_XMMu32_XMMu32_IMM8_AVX512EVEX.128.66.0F3A.W0 71 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDD xmm {k}{z}, xmm, m128/m32bcst, imm8 VPSHLDD_XMMu32_MASKmskw_XMMu32_MEMu32_IMM8_AVX512EVEX.128.66.0F3A.W0 71 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDD ymm {k}{z}, ymm, ymm, imm8 VPSHLDD_YMMu32_MASKmskw_YMMu32_YMMu32_IMM8_AVX512EVEX.256.66.0F3A.W0 71 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDD ymm {k}{z}, ymm, m256/m32bcst, imm8 VPSHLDD_YMMu32_MASKmskw_YMMu32_MEMu32_IMM8_AVX512EVEX.256.66.0F3A.W0 71 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDD zmm {k}{z}, zmm, zmm, imm8 VPSHLDD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_IMM8_AVX512EVEX.512.66.0F3A.W0 71 /r ibAVX10.1 or AVX512_VBMI2
VPSHLDD zmm {k}{z}, zmm, m512/m32bcst, imm8 VPSHLDD_ZMMu32_MASKmskw_ZMMu32_MEMu32_IMM8_AVX512EVEX.512.66.0F3A.W0 71 /r ibAVX10.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.
Modelxmm {k}{z}, xmm, xmm, imm8no mask
ymm {k}{z}, ymm, ymm, imm8no mask
xmm {k}{z}, xmm, xmm, imm8with a mask, zeroing
ymm {k}{z}, ymm, ymm, imm8with a mask, zeroing
xmm {k}{z}, xmm, m128/m32bcst, imm8no mask, broadcastxmm {k}{z}, xmm, m128/m32bcst, imm8with a mask, zeroingymm {k}{z}, ymm, m256/m32bcst, imm8no mask, broadcastymm {k}{z}, ymm, m256/m32bcst, imm8with a mask, zeroingzmm {k}{z}, zmm, zmm, imm8no maskzmm {k}{z}, zmm, zmm, imm8with a mask, zeroingzmm {k}{z}, zmm, m512/m32bcst, imm8no mask, broadcastzmm {k}{z}, zmm, m512/m32bcst, imm8with a mask, zeroing
Ice Lake5 / 0.5p015 / 0.5p0111 / 0.5p0111 / 0.5p0112 / 0.5p0112 / 0.5p015 / 0.5p055 / 0.5p0512 / 0.5p0512 / 0.5p05
Sapphire Rapids1 / 0.5p012 / 0.67p0158 / 0.5p019 / 0.67p0159 / 0.5p0110 / 0.67p0151 / 1p02 / 1p059 / 1p010 / 1p05
Zen 42 / 11FP0 FP12 / 11FP0 FP110 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP32 / 1FP0 FP12 / 1FP0 FP110 / 1FP0 FP310 / 1FP0 FP3
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2834; AMD 58455, row 926).

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: each doubleword of the result comes from the doubleword in the same place in each source.
VPSHLDD: element by elementResult doubleword i comes from doubleword i of xmm2 and xmm3. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2a1110k1r0r1r3xmm10123xmm3or m128b

Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms. The 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 and xmm3. 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.

for i in range(VL // 32):
    if k1[i]:
        a = zmm2.d[i]
        b = src3.d[i]
        x = a << 32 | b
        zmm1.d[i] = x << (imm8 & 31) >> 32
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 6 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
VPSHLDD xmm {k}{z}, xmm, xmm/m128/m32bcst, imm8 VPSHLDD ymm {k}{z}, ymm, ymm/m256/m32bcst, imm8 VPSHLDD zmm {k}{z}, zmm, zmm/m512/m32bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
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.

All forms
AVX512-E4

Attributes

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

All forms
write masking
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSHLDD, 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_shldi_epi32 __m128i _mm_shldi_epi32(__m128i A, __m128i B, const int I)

VPSHLDD xmm, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_shrdi_epi32 __m128i _mm_shrdi_epi32(__m128i A, __m128i B, const int I)

VPSHLDD xmm, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_mask_shldi_epi32 __m128i _mm_mask_shldi_epi32(__m128i S, __mmask8 U, __m128i A, __m128i B, const int I)

VPSHLDD xmm {k}, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_mask_shrdi_epi32 __m128i _mm_mask_shrdi_epi32(__m128i S, __mmask8 U, __m128i A, __m128i B, const int I)

VPSHLDD xmm {k}, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_maskz_shldi_epi32 __m128i _mm_maskz_shldi_epi32(__mmask8 U, __m128i A, __m128i B, const int I)

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

_mm_maskz_shrdi_epi32 __m128i _mm_maskz_shrdi_epi32(__mmask8 U, __m128i A, __m128i B, const int I)

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

_mm256_shldi_epi32 __m256i _mm256_shldi_epi32(__m256i A, __m256i B, const int I)

VPSHLDD ymm, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_shrdi_epi32 __m256i _mm256_shrdi_epi32(__m256i A, __m256i B, const int I)

VPSHLDD ymm, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_mask_shldi_epi32 __m256i _mm256_mask_shldi_epi32(__m256i S, __mmask8 U, __m256i A, __m256i B, const int I)

VPSHLDD ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_mask_shrdi_epi32 __m256i _mm256_mask_shrdi_epi32(__m256i S, __mmask8 U, __m256i A, __m256i B, const int I)

VPSHLDD ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_maskz_shldi_epi32 __m256i _mm256_maskz_shldi_epi32(__mmask8 U, __m256i A, __m256i B, const int I)

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

_mm256_maskz_shrdi_epi32 __m256i _mm256_maskz_shrdi_epi32(__mmask8 U, __m256i A, __m256i B, const int I)

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

_mm512_shldi_epi32 __m512i _mm512_shldi_epi32(__m512i A, __m512i B, const int I)

VPSHLDD zmm, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_shrdi_epi32 __m512i _mm512_shrdi_epi32(__m512i A, __m512i B, const int I)

VPSHLDD zmm, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_mask_shldi_epi32 __m512i _mm512_mask_shldi_epi32(__m512i S, __mmask16 U, __m512i A, __m512i B, const int I)

VPSHLDD zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_mask_shrdi_epi32 __m512i _mm512_mask_shrdi_epi32(__m512i S, __mmask16 U, __m512i A, __m512i B, const int I)

VPSHLDD zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_maskz_shldi_epi32 __m512i _mm512_maskz_shldi_epi32(__mmask16 U, __m512i A, __m512i B, const int I)

VPSHLDD zmm {k}{z}, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_maskz_shrdi_epi32 __m512i _mm512_maskz_shrdi_epi32(__mmask16 U, __m512i A, __m512i B, const int I)

VPSHLDD zmm {k}{z}, zmm, zmm, imm8 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-622 (VPSHLD)
  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.