Instruction
VPSHRDQ
Joins each quadword of the second source above the matching one of the first, shifts the pair right by an immediate and keeps the lower half.
- 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], 0x0every selected element came from YMM8. - One register twice is a rotate.
vpshrdq ymm24{k5}{z}, ymm3, ymm3, 0x7fturned 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
| Instruction | Encoding | Requires |
|---|---|---|
VPSHRDQ xmm {k}{z}, xmm, xmm, imm8
VPSHRDQ_XMMu64_MASKmskw_XMMu64_XMMu64_IMM8_AVX512 | EVEX.128.66.0F3A.W1 73 /r ib | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDQ xmm {k}{z}, xmm, m128/m64bcst, imm8
VPSHRDQ_XMMu64_MASKmskw_XMMu64_MEMu64_IMM8_AVX512 | EVEX.128.66.0F3A.W1 73 /r ib | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDQ ymm {k}{z}, ymm, ymm, imm8
VPSHRDQ_YMMu64_MASKmskw_YMMu64_YMMu64_IMM8_AVX512 | EVEX.256.66.0F3A.W1 73 /r ib | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDQ ymm {k}{z}, ymm, m256/m64bcst, imm8
VPSHRDQ_YMMu64_MASKmskw_YMMu64_MEMu64_IMM8_AVX512 | EVEX.256.66.0F3A.W1 73 /r ib | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDQ zmm {k}{z}, zmm, zmm, imm8
VPSHRDQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_IMM8_AVX512 | EVEX.512.66.0F3A.W1 73 /r ib | AVX10.1 or AVX512_VBMI2 |
VPSHRDQ zmm {k}{z}, zmm, m512/m64bcst, imm8
VPSHRDQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_IMM8_AVX512 | EVEX.512.66.0F3A.W1 73 /r ib | AVX10.1 or AVX512_VBMI2 |
Latency and throughput
| Model | xmm {k}{z}, xmm, xmm, imm8no maskymm {k}{z}, ymm, ymm, imm8no mask | xmm {k}{z}, xmm, xmm, imm8with a mask, zeroingymm {k}{z}, ymm, ymm, imm8with a mask, zeroing | xmm {k}{z}, xmm, m128/m64bcst, imm8no mask, broadcast | xmm {k}{z}, xmm, m128/m64bcst, imm8with a mask, zeroing | ymm {k}{z}, ymm, m256/m64bcst, imm8no mask, broadcast | ymm {k}{z}, ymm, m256/m64bcst, imm8with a mask, zeroing | zmm {k}{z}, zmm, zmm, imm8no mask | zmm {k}{z}, zmm, zmm, imm8with a mask, zeroing | zmm {k}{z}, zmm, m512/m64bcst, imm8no mask, broadcast | zmm {k}{z}, zmm, m512/m64bcst, imm8with a mask, zeroing |
|---|---|---|---|---|---|---|---|---|---|---|
| Ice Lake | 5 / 0.5p01 | 5 / 0.5p01 | 11 / 0.5p01 | 11 / 0.5p01 | 12 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p05 | 5 / 0.5p05 | 12 / 0.5p05 | 12 / 0.5p05 |
| Sapphire Rapids | 1 / 0.5p01 | 2 / 0.67p015 | 8 / 0.5p01 | 9 / 0.67p015 | 9 / 0.5p01 | 10 / 0.67p015 | 1 / 1p0 | 2 / 1p05 | 9 / 1p0 | 10 / 1p05 |
| Zen 4 | 2 / 1FP0 FP1 | 2 / 1FP0 FP1 | 10 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 2 / 1FP0 FP1 | 2 / 1FP0 FP1 | 10 / 1FP0 FP3 | 10 / 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.
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 upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
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, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | explicit | read |
imm8 | explicit | read |
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512_VBMI2_128 | AVX10.1 or AVX512_VBMI2 + 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_128 | Same as AVX512_VBMI2_128 |
AVX512_VBMI2_512 | AVX10.1 or AVX512_VBMI2 | Same as AVX512_VBMI2_128 |
More AVX10.1 instructions
- VPROLD
- VPROLQ
- VPROLVD
- VPROLVQ
- VPRORD
- VPRORQ
- VPRORVD
- VPRORVQ
- VPSADBW
- VPSCATTERDD
- VPSCATTERDQ
- VPSCATTERQD
- VPSCATTERQQ
- VPSHLDD
- VPSHLDQ
- VPSHLDVD
- VPSHLDVQ
- VPSHLDVW
- VPSHLDW
- VPSHRDD
- VPSHRDVD
- VPSHRDVQ
- VPSHRDVW
- VPSHRDW
- VPSHUFB
- VPSHUFBITQMB
- VPSHUFD
- VPSHUFHW
- VPSHUFLW
- VPSLLD
- VPSLLDQ
- VPSLLQ
- VPSLLVD
- VPSLLVQ
- VPSLLVW
- VPSLLW
- VPSRAD
- VPSRAQ
- VPSRAVD
- VPSRAVQ
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-628 (VPSHRD)
- 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.