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

VPSHRDQ is the quadword form of VPSHRDD, whose page explains which source goes where, and the right-shifting twin of VPSHLDQ: each quadword of the second source is joined above the matching quadword of the first, the 128-bit pair is shifted right by the immediate, taken modulo 64, and the low 64 bits are kept. It is what SHRD does to two 64-bit registers, for up to eight pairs at once. It belongs to AVX512_VBMI2, which -march=znver5 enables and x86-64-v4 does not, and takes masking and a broadcast quadword.

Recorded on Zen 5

  • Counts modulo 64. FFh and 7Fh both shifted by 63: 1 under FFFFFFFFFFFFFFFFh gave FFFFFFFFFFFFFFFEh, the second source moved up by one with bit 63 of the first below it, and 8000000000000000h under 7FFFFFFFFFFFFFFFh gave all ones.
  • A count of 0 returned the first source: in vpshrdq ymm14{k3}, ymm8, ymmword ptr [mem], 0x0 every selected element came from YMM8.
  • One register twice is a rotate. vpshrdq ymm24{k5}{z}, ymm3, ymm3, 0x7f turned 8 into 10h, a rotate right by 63, which is a rotate left by one.

In compiled code

The compilers prefer the left-shifting form. With -march=znver5, Clang 23 at -O2 compiles (lo[i] >> 13) | (hi[i] << 51) over uint64_t arrays, and the intrinsic _mm512_shrdi_epi64(a, b, 13) too, to VPSHLDQ by 51 with the sources swapped; GCC 14 keeps the loop as VPSRLQ, VPSLLQ and VPORQ, and emits VPSHRDQ only for the intrinsic, masked or not. Shifting a long bit string right by 13, with each element’s high bits taken from the next one, Clang lines up the neighbours with VALIGNQ and again uses VPSHLDQ, while GCC leaves that loop scalar.

AMD’s Zen 5 latency spreadsheet gives VPSHRDQ 2 cycles and two per cycle on pipes FP0 and FP1, as VPSHRDD.

Forms

Every encoding of VPSHRDQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSHRDQ xmm {k}{z}, xmm, xmm, imm8 VPSHRDQ_XMMu64_MASKmskw_XMMu64_XMMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDQ xmm {k}{z}, xmm, m128/m64bcst, imm8 VPSHRDQ_XMMu64_MASKmskw_XMMu64_MEMu64_IMM8_AVX512EVEX.128.66.0F3A.W1 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDQ ymm {k}{z}, ymm, ymm, imm8 VPSHRDQ_YMMu64_MASKmskw_YMMu64_YMMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDQ ymm {k}{z}, ymm, m256/m64bcst, imm8 VPSHRDQ_YMMu64_MASKmskw_YMMu64_MEMu64_IMM8_AVX512EVEX.256.66.0F3A.W1 73 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDQ zmm {k}{z}, zmm, zmm, imm8 VPSHRDQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 73 /r ibAVX10.1 or AVX512_VBMI2
VPSHRDQ zmm {k}{z}, zmm, m512/m64bcst, imm8 VPSHRDQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_IMM8_AVX512EVEX.512.66.0F3A.W1 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/m64bcst, imm8no mask, broadcastxmm {k}{z}, xmm, m128/m64bcst, imm8with a mask, zeroingymm {k}{z}, ymm, m256/m64bcst, imm8no mask, broadcastymm {k}{z}, ymm, m256/m64bcst, imm8with a mask, zeroingzmm {k}{z}, zmm, zmm, imm8no maskzmm {k}{z}, zmm, zmm, imm8with a mask, zeroingzmm {k}{z}, zmm, m512/m64bcst, imm8no mask, broadcastzmm {k}{z}, zmm, m512/m64bcst, 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 / 1FP0 FP12 / 1FP0 FP110 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP32 / 1FP0 FP12 / 1FP0 FP110 / 1FP0 FP310 / 1FP0 FP3

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 quadword of the result comes from the quadword in the same place in each source.
VPSHRDQ: element by elementResult quadword i comes from quadword i of xmm2 and xmm3. Result quadwords 1 to 0: r1, r0.01xmm2a11k1r0r1xmm101xmm3or m128b

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

Result quadword i comes from quadword i of xmm2 and xmm3. 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.

for i in range(VL // 64):
    if k1[i]:
        a = zmm2.q[i]
        b = src3.q[i]
        x = b << 64 | a
        zmm1.q[i] = x >> (imm8 & 63)
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src3.q[i] is the m64 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
VPSHRDQ xmm {k}{z}, xmm, xmm/m128/m64bcst, imm8 VPSHRDQ ymm {k}{z}, ymm, ymm/m256/m64bcst, imm8 VPSHRDQ zmm {k}{z}, zmm, zmm/m512/m64bcst, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
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.

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)
  6. 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 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.