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

VPSHRDD is the right-shifting twin of VPSHLDD, whose page explains funnel shifts and their uses. Per doubleword it joins the second source above the first, shifts the 64-bit pair right by the immediate, taken modulo 32, and keeps the lower 32 bits: the bits shifted out of the first source are replaced by the low bits of the second, as SHRD does for general-purpose registers.

Which half is which

Both instructions keep the bits of the first source and fill in from the second, but the halves swap places: VPSHLDD puts the first source on top, VPSHRDD at the bottom. A right shift by n is therefore the same as a left shift by 32 - n with the sources exchanged. The cases recorded on Zen 5 show the edges:

  • an immediate of 0 returns the first source unchanged;
  • 1Fh gives the second source shifted left by one, with the top bit of the first below it: 7FFFFFFFh under 00000001h gave 00000002h;
  • with the same register as both sources it is a rotate right, and an immediate of 21h acted as 1, turning 00000001h into 80000000h and 7FFFFFFFh into BFFFFFFFh.

In compiled code

The instruction needs AVX512_VBMI2; -march=znver5 enables it, x86-64-v4 does not. At -O2 with that target:

  • GCC 14 compiles _mm512_shrdi_epi32(a, b, 5) to vpshrdd zmm0, zmm0, zmm1, 5.
  • Clang 23 compiles the same intrinsic to vpshldd zmm0, zmm1, zmm0, 27, the equivalent left shift. It does so for every _shrdi_ intrinsic, which is why they are listed on the VPSHLDD page and this page lists none.
  • For (a >> 5) | (b << 27) on vectors of uint32_t, Clang emits the same VPSHLDD; GCC keeps two shifts and an OR, and for a loop of (a[i] >> 5) | (a[i+1] << 27), scalar SHLD.

VPSHRDVD takes a count per element, and VPSHRDQ and VPSHRDW work on quadwords and words.

Forms

Every encoding of VPSHRDD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSHRDD xmm {k}{z}, xmm, xmm, imm8 VPSHRDD_XMMu32_MASKmskw_XMMu32_XMMu32_IMM8_AVX512EVEX.128.66.0F3A.W0 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDD xmm {k}{z}, xmm, m128/m32bcst, imm8 VPSHRDD_XMMu32_MASKmskw_XMMu32_MEMu32_IMM8_AVX512EVEX.128.66.0F3A.W0 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDD ymm {k}{z}, ymm, ymm, imm8 VPSHRDD_YMMu32_MASKmskw_YMMu32_YMMu32_IMM8_AVX512EVEX.256.66.0F3A.W0 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDD ymm {k}{z}, ymm, m256/m32bcst, imm8 VPSHRDD_YMMu32_MASKmskw_YMMu32_MEMu32_IMM8_AVX512EVEX.256.66.0F3A.W0 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDD zmm {k}{z}, zmm, zmm, imm8 VPSHRDD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_IMM8_AVX512EVEX.512.66.0F3A.W0 73 /r ibAVX10.1 or AVX512_VBMI2
VPSHRDD zmm {k}{z}, zmm, m512/m32bcst, imm8 VPSHRDD_ZMMu32_MASKmskw_ZMMu32_MEMu32_IMM8_AVX512EVEX.512.66.0F3A.W0 73 /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 2854; AMD 58455, row 932).

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.
VPSHRDD: 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 = b << 32 | a
        zmm1.d[i] = x >> (imm8 & 31)
    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
VPSHRDD xmm {k}{z}, xmm, xmm/m128/m32bcst, imm8 VPSHRDD ymm {k}{z}, ymm, ymm/m256/m32bcst, imm8 VPSHRDD 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

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. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  4. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-628 (VPSHRD)

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 timings come from LLVM's scheduling models, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.