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

VPSHRDVW is the word form of VPSHRDVD: each word of the first source is joined above the matching word of the destination, the 32-bit pair is shifted right by the count in the matching word of the second source, and the lower 16 bits are written back to the destination. VPSHRDVD’s page explains why the destination is the lower half; VPSHLDVW shifts left and VPSHRDW takes one immediate count. Only bits 3:0 of each count matter, and the second source has no broadcast form. It belongs to AVX512_VBMI2, which x86-64-v4 lacks and -march=znver5 enables.

Recorded on Zen 5

  • A funnel. In {evex} vpshrdvw xmm24, xmm3, xmm3, a destination word of 0 under 007Fh, shifted right by 15 (7Fh modulo 16), gave 00FEh: seven bits of the upper half came down into the lower one.
  • A rotate. With one register three times, as in vpshrdvw zmm5{k1}, zmm5, zmm5, each word is rotated right by itself: 7FFFh, a count of 15, became FFFEh, a rotate left by one.

In compiled code

At -O2 with -march=znver5, Clang 23 compiles a loop of variable right rotates of uint16_t, (h[i] >> n) | (h[i] << ((16 - n) & 15)) with n = c[i] & 15, to VPSHRDVW with the same register as both halves; GCC 14 uses VPSRLVW, VPSLLVW and an OR. A shift right of two uint16_t arrays joined into 32 bits is widened to doublewords by both. _mm512_shrdv_epi16(a, b, c) is one VPSHRDVW, a the lower half and the register written.

AMD’s Zen 5 latency spreadsheet gives one macro-op on pipe FP0 or FP1 and 2 cycles, two per cycle, the figures of every VBMI2 funnel shift.

Forms

Every encoding of VPSHRDVW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSHRDVW xmm {k}{z}, xmm, xmm VPSHRDVW_XMMu16_MASKmskw_XMMu16_XMMu16_AVX512EVEX.128.66.0F38.W1 72 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVW xmm {k}{z}, xmm, m128 VPSHRDVW_XMMu16_MASKmskw_XMMu16_MEMu16_AVX512EVEX.128.66.0F38.W1 72 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVW ymm {k}{z}, ymm, ymm VPSHRDVW_YMMu16_MASKmskw_YMMu16_YMMu16_AVX512EVEX.256.66.0F38.W1 72 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVW ymm {k}{z}, ymm, m256 VPSHRDVW_YMMu16_MASKmskw_YMMu16_MEMu16_AVX512EVEX.256.66.0F38.W1 72 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVW zmm {k}{z}, zmm, zmm VPSHRDVW_ZMMu16_MASKmskw_ZMMu16_ZMMu16_AVX512EVEX.512.66.0F38.W1 72 /rAVX10.1 or AVX512_VBMI2
VPSHRDVW zmm {k}{z}, zmm, m512 VPSHRDVW_ZMMu16_MASKmskw_ZMMu16_MEMu16_AVX512EVEX.512.66.0F38.W1 72 /rAVX10.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, xmmno mask
ymm {k}{z}, ymm, ymmno mask
xmm {k}{z}, xmm, xmmwith a mask, zeroing
ymm {k}{z}, ymm, ymmwith a mask, zeroing
xmm {k}{z}, xmm, m128no maskxmm {k}{z}, xmm, m128with a mask, zeroingymm {k}{z}, ymm, m256no maskymm {k}{z}, ymm, m256with a mask, zeroingzmm {k}{z}, zmm, zmmno maskzmm {k}{z}, zmm, zmmwith a mask, zeroingzmm {k}{z}, zmm, m512no maskzmm {k}{z}, zmm, m512with 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.5p013 / 0.5p018 / 0.5p0111 / 0.5p019 / 0.5p0111 / 0.5p011 / 1p03 / 1p09 / 1p011 / 1p0
Zen 43 / 0.5FP0 FP32 / 1FP0 FP110 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP310 / 0.5FP0 FP33 / 1FP0 FP32 / 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 word of the result comes from the word in the same place in each source.
VPSHRDVW: element by elementResult word i comes from word i of xmm1, xmm2 and xmm3. Result words 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, r1, r0.01234567xmm1a01234567xmm2b01234567xmm3or m128c11111110k1r0r1r2r3r4r5r7xmm1

Every word works alike: 8, 16 and 32 words 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}. The sources are drawn above the result, each element in its own column.

Result word i comes from word i of xmm1, xmm2 and xmm3. Result words 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, 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 // 16):
    if k1[i]:
        a = zmm1.w[i]
        b = zmm2.w[i]
        c = src3.w[i]
        x = b << 16 | a
        zmm1.w[i] = x >> (c & 15)
    elif zeroing:
        zmm1.w[i] = 0
    # else: zmm1.w[i] keeps its value
# 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
VPSHRDVW xmm {k}{z}, xmm, xmm/m128 VPSHRDVW ymm {k}{z}, ymm, ymm/m256 VPSHRDVW zmm {k}{z}, zmm, zmm/m512
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128, ymm/m256, zmm/m512explicitread

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
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSHRDVW, 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_shrdv_epi16 __m128i _mm_shrdv_epi16(__m128i __A, __m128i __B, __m128i __C)

VPSHRDVW xmm, xmm, xmm EVEX.128 -mavx512vl -mavx512vbmi2

_mm_mask_shrdv_epi16 __m128i _mm_mask_shrdv_epi16(__m128i __A, __mmask8 __U, __m128i __B, __m128i __C)

VPSHRDVW xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512vbmi2

_mm_maskz_shrdv_epi16 __m128i _mm_maskz_shrdv_epi16(__mmask8 __U, __m128i __A, __m128i __B, __m128i __C)

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

_mm256_shrdv_epi16 __m256i _mm256_shrdv_epi16(__m256i __A, __m256i __B, __m256i __C)

VPSHRDVW ymm, ymm, ymm EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_mask_shrdv_epi16 __m256i _mm256_mask_shrdv_epi16(__m256i __A, __mmask16 __U, __m256i __B, __m256i __C)

VPSHRDVW ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_maskz_shrdv_epi16 __m256i _mm256_maskz_shrdv_epi16(__mmask16 __U, __m256i __A, __m256i __B, __m256i __C)

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

_mm512_shrdv_epi16 __m512i _mm512_shrdv_epi16(__m512i __A, __m512i __B, __m512i __C)

VPSHRDVW zmm, zmm, zmm EVEX.512 -mavx512vbmi2

_mm512_mask_shrdv_epi16 __m512i _mm512_mask_shrdv_epi16(__m512i __A, __mmask32 __U, __m512i __B, __m512i __C)

VPSHRDVW zmm {k}, zmm, zmm EVEX.512 -mavx512vbmi2

_mm512_maskz_shrdv_epi16 __m512i _mm512_maskz_shrdv_epi16(__mmask32 __U, __m512i __A, __m512i __B, __m512i __C)

VPSHRDVW zmm {k}{z}, zmm, zmm 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-631 (VPSHRDV)
  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.