Instruction
VPSHRDVD
Joins each doubleword of the source above the matching one of the destination, shifts the pair right by a per-element count and keeps the lower half.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPSHRDVD is the variable form of VPSHRDD: per doubleword, the matching element of the first source is joined above the destination’s, the 64-bit pair is shifted right by a count from the second source, and the lower 32 bits are kept. Its left-shifting twin, VPSHLDVD, explains the three-input form and why only bits 4:0 of a count matter.
The destination is the lower half
In both variable funnel shifts the destination holds the half whose
bits survive the shift, but here that is the lower half: the result is
the destination shifted right, filled from the top with the low bits
of the first source. In _mm512_shrdv_epi32(a, b, c), a is the
lower half and the register written, b the upper half and c the
counts. With the same register as destination and first source it is
a rotate right per element: on Zen 5, a broadcast count of 0C337E85h,
which is 5 modulo 32, turned 80000000h into 04000000h and 7FFFFFFFh
into FBFFFFFFh.
Counts wrap at 32, as the recorded cases show: a count of 80h acted as 0 and returned the destination unchanged, and 7Fh acted as 31, so 7FFFFFFFh under 00000001h became 00000002h. The plain shift VPSRLVD gives zero for any count above 31 instead.
In compiled code
At -O2 with -march=znver5, which enables AVX512_VBMI2:
- Clang 23 compiles a loop of
s ? (a[i] >> s) | (b[i] << (32 - s)) : a[i], withs = c[i] & 31, to VPSHRDVD under a write mask that stands for the test of s against zero, and uses scalar SHRD for the last elements. - GCC 14 keeps that loop scalar, with SHRX and SHLX.
_mm512_shrdv_epi32gives VPSHRDVD in both compilers. Unlike the immediate form, which Clang rewrites as a left shift, the variable form stays a right shift.
VPSHRDVQ and VPSHRDVW work on quadwords and words.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPSHRDVD xmm {k}{z}, xmm, xmm
VPSHRDVD_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512 | EVEX.128.66.0F38.W0 73 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDVD xmm {k}{z}, xmm, m128/m32bcst
VPSHRDVD_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512 | EVEX.128.66.0F38.W0 73 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDVD ymm {k}{z}, ymm, ymm
VPSHRDVD_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512 | EVEX.256.66.0F38.W0 73 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDVD ymm {k}{z}, ymm, m256/m32bcst
VPSHRDVD_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512 | EVEX.256.66.0F38.W0 73 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPSHRDVD zmm {k}{z}, zmm, zmm
VPSHRDVD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512 | EVEX.512.66.0F38.W0 73 /r | AVX10.1 or AVX512_VBMI2 |
VPSHRDVD zmm {k}{z}, zmm, m512/m32bcst
VPSHRDVD_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512 | EVEX.512.66.0F38.W0 73 /r | AVX10.1 or AVX512_VBMI2 |
Latency and throughput
| Model | xmm {k}{z}, xmm, xmmno maskymm {k}{z}, ymm, ymmno mask | xmm {k}{z}, xmm, xmmwith a mask, zeroingymm {k}{z}, ymm, ymmwith a mask, zeroing | xmm {k}{z}, xmm, m128/m32bcst | ymm {k}{z}, ymm, m256/m32bcst | zmm {k}{z}, zmm, zmmno mask | zmm {k}{z}, zmm, zmmwith a mask, zeroing | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|---|
| Ice Lake | 5 / 0.5p01 | 5 / 0.5p01 | 11 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p05 | 5 / 0.5p05 | 12 / 0.5p05 |
| Sapphire Rapids | 1 / 0.5p01 | 1 / 0.5p01 | 8 / 0.5p01 | 9 / 0.5p01 | 1 / 1p0 | 1 / 1p0 | 9 / 1p0 |
| Zen 4 | 3 / 0.51FP0 FP3 | 2 / 12FP0 FP1 | 10 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 3 / 13FP0 FP3 | 2 / 1FP0 FP1 | 10 / 1FP0 FP3 |
- Zen 4 model: AMD's spreadsheets give latency 2 for Zen 4 and Zen 5 (AMD 57647, row 2860; AMD 58455, row 935).
- Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2860; AMD 58455, row 935).
- Zen 4 model: AMD's spreadsheets give latency 2 for Zen 4 and Zen 5 (AMD 57647, row 2862; AMD 58455, row 935).
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 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. The sources are drawn above the result, each element in its own column.
Result doubleword i comes from doubleword i of xmm1, 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 = zmm1.d[i]
b = zmm2.d[i]
c = src3.d[i]
x = b << 32 | a
zmm1.d[i] = x >> (c & 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 upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPSHRDVD xmm {k}{z}, xmm, xmm/m128/m32bcst VPSHRDVD ymm {k}{z}, ymm, ymm/m256/m32bcst VPSHRDVD zmm {k}{z}, zmm, zmm/m512/m32bcst | ||
xmm, ymm, zmm | explicit | read, write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | 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
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VPSHRDVD, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_shrdv_epi32
__m128i _mm_shrdv_epi32(__m128i __A, __m128i __B, __m128i __C) |
|
_mm_mask_shrdv_epi32
__m128i _mm_mask_shrdv_epi32(__m128i __A, __mmask8 __U, __m128i __B, __m128i __C) |
|
_mm_maskz_shrdv_epi32
__m128i _mm_maskz_shrdv_epi32(__mmask8 __U, __m128i __A, __m128i __B, __m128i __C) |
|
_mm256_shrdv_epi32
__m256i _mm256_shrdv_epi32(__m256i __A, __m256i __B, __m256i __C) |
|
_mm256_mask_shrdv_epi32
__m256i _mm256_mask_shrdv_epi32(__m256i __A, __mmask8 __U, __m256i __B, __m256i __C) |
|
_mm256_maskz_shrdv_epi32
__m256i _mm256_maskz_shrdv_epi32(__mmask8 __U, __m256i __A, __m256i __B, __m256i __C) |
|
_mm512_shrdv_epi32
__m512i _mm512_shrdv_epi32(__m512i __A, __m512i __B, __m512i __C) |
|
_mm512_mask_shrdv_epi32
__m512i _mm512_mask_shrdv_epi32(__m512i __A, __mmask16 __U, __m512i __B, __m512i __C) |
|
_mm512_maskz_shrdv_epi32
__m512i _mm512_maskz_shrdv_epi32(__mmask16 __U, __m512i __A, __m512i __B, __m512i __C) |
|
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
- VPROLQ
- VPROLVD
- VPROLVQ
- VPRORD
- VPRORQ
- VPRORVD
- VPRORVQ
- VPSADBW
- VPSCATTERDD
- VPSCATTERDQ
- VPSCATTERQD
- VPSCATTERQQ
- VPSHLDD
- VPSHLDQ
- VPSHLDVD
- VPSHLDVQ
- VPSHLDVW
- VPSHLDW
- VPSHRDD
- VPSHRDQ
- VPSHRDVQ
- VPSHRDVW
- VPSHRDW
- VPSHUFB
- VPSHUFBITQMB
- VPSHUFD
- VPSHUFHW
- VPSHUFLW
- VPSLLD
- VPSLLDQ
- VPSLLQ
- VPSLLVD
- VPSLLVQ
- VPSLLVW
- VPSLLW
- VPSRAD
- VPSRAQ
- VPSRAVD
- VPSRAVQ
- VPSRAVW
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. - 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. - 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-631 (VPSHRDV)
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.