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

VPSHLDW is the word form of VPSHLDD, whose page explains the funnel shift: each word of the first source is joined above the matching word of the second, the 32-bit pair is shifted left by the immediate and the upper 16 bits are kept. Only bits 3:0 of the immediate count. Like the rest of AVX512_VBMI2 it is not part of x86-64-v4; -march=znver5 includes it.

Recorded on Zen 5

  • vpshldw xmm9, xmm9, xmm14, 0x1 shifted 7FFFh up by one and filled the low bit from FFFFh, giving FFFFh, and turned 8000h above 8000h into 0001h: the top bit of the first source fell out, the top bit of the second came in.
  • Counts wrap at 16. With 10h, vpshldw zmm24{k3}, zmm3, [mem], 0x10 wrote the words of ZMM3 unchanged to the elements K3 selects. With FFh, acting as 15, {evex} vpshldw ymm0, ymm31, [mem], 0xff kept only the low bit of each word of YMM31, now on top, above the high 15 bits of the memory word: 8000h above FFFFh gave 7FFFh.

In compiled code

Built with -march=znver5 at -O2, Clang 23 uses VPSHLDW for 16-bit rotates and funnel shifts written in C: over uint16_t arrays, (a[i] << 3) | (a[i] >> 13) becomes vpshldw zmm0, zmm0, zmm0, 3 and (a[i] << 3) | (b[i] >> 13) a VPSHLDW that reads b from memory. GCC 14 compiles both to VPSLLW, VPSRLW and VPORQ, and emits VPSHLDW only for the intrinsic _mm512_shldi_epi16. It passes a count of 16 or 17 to the assembler as written; Clang returns the first operand unchanged for 16, with no instruction, and reduces 17 to 1.

AVX-512 has no word rotate, so the funnel shift with one register twice is the one-instruction way to rotate words.

AMD’s Zen 5 latency spreadsheet gives VPSHLDW 2 cycles and two per cycle on pipes FP0 and FP1, as VPSHLDD. Zen 5’s 6 recorded cases cover the register and memory forms at all three widths.

Forms

Every encoding of VPSHLDW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSHLDW xmm {k}{z}, xmm, xmm, imm8 VPSHLDW_XMMu16_MASKmskw_XMMu16_XMMu16_IMM8_AVX512EVEX.128.66.0F3A.W1 70 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDW xmm {k}{z}, xmm, m128, imm8 VPSHLDW_XMMu16_MASKmskw_XMMu16_MEMu16_IMM8_AVX512EVEX.128.66.0F3A.W1 70 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDW ymm {k}{z}, ymm, ymm, imm8 VPSHLDW_YMMu16_MASKmskw_YMMu16_YMMu16_IMM8_AVX512EVEX.256.66.0F3A.W1 70 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDW ymm {k}{z}, ymm, m256, imm8 VPSHLDW_YMMu16_MASKmskw_YMMu16_MEMu16_IMM8_AVX512EVEX.256.66.0F3A.W1 70 /r ibAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHLDW zmm {k}{z}, zmm, zmm, imm8 VPSHLDW_ZMMu16_MASKmskw_ZMMu16_ZMMu16_IMM8_AVX512EVEX.512.66.0F3A.W1 70 /r ibAVX10.1 or AVX512_VBMI2
VPSHLDW zmm {k}{z}, zmm, m512, imm8 VPSHLDW_ZMMu16_MASKmskw_ZMMu16_MEMu16_IMM8_AVX512EVEX.512.66.0F3A.W1 70 /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, imm8no maskxmm {k}{z}, xmm, m128, imm8with a mask, zeroingymm {k}{z}, ymm, m256, imm8no maskymm {k}{z}, ymm, m256, imm8with a mask, zeroingzmm {k}{z}, zmm, zmm, imm8no maskzmm {k}{z}, zmm, zmm, imm8with a mask, zeroingzmm {k}{z}, zmm, m512, imm8no maskzmm {k}{z}, zmm, m512, 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.5p014 / 0.67p0158 / 0.5p0111 / 0.67p0159 / 0.5p0112 / 0.67p0151 / 1p04 / 1p059 / 1p012 / 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 2849; AMD 58455, row 925).

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.
VPSHLDW: element by elementResult word i comes from word i of xmm2 and xmm3. Result words 7 to 0: r7, unchanged (bit 6 of k1 is 0), r5, r4, r3, r2, r1, r0.01234567xmm2a11111110k1r0r1r2r3r4r5r7xmm101234567xmm3or m128b

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}.

Result word i comes from word i of 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 = zmm2.w[i]
        b = src3.w[i]
        x = a << 16 | b
        zmm1.w[i] = x << (imm8 & 15) >> 16
    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
VPSHLDW xmm {k}{z}, xmm, xmm/m128, imm8 VPSHLDW ymm {k}{z}, ymm, ymm/m256, imm8 VPSHLDW zmm {k}{z}, zmm, zmm/m512, imm8
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128, ymm/m256, zmm/m512explicitread
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
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSHLDW, 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_shldi_epi16 __m128i _mm_shldi_epi16(__m128i A, __m128i B, const int I)

VPSHLDW xmm, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_shrdi_epi16 __m128i _mm_shrdi_epi16(__m128i A, __m128i B, const int I)

VPSHLDW xmm, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_mask_shldi_epi16 __m128i _mm_mask_shldi_epi16(__m128i S, __mmask8 U, __m128i A, __m128i B, const int I)

VPSHLDW xmm {k}, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_mask_shrdi_epi16 __m128i _mm_mask_shrdi_epi16(__m128i S, __mmask8 U, __m128i A, __m128i B, const int I)

VPSHLDW xmm {k}, xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512vbmi2

_mm_maskz_shldi_epi16 __m128i _mm_maskz_shldi_epi16(__mmask8 U, __m128i A, __m128i B, const int I)

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

_mm_maskz_shrdi_epi16 __m128i _mm_maskz_shrdi_epi16(__mmask8 U, __m128i A, __m128i B, const int I)

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

_mm256_shldi_epi16 __m256i _mm256_shldi_epi16(__m256i A, __m256i B, const int I)

VPSHLDW ymm, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_shrdi_epi16 __m256i _mm256_shrdi_epi16(__m256i A, __m256i B, const int I)

VPSHLDW ymm, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_mask_shldi_epi16 __m256i _mm256_mask_shldi_epi16(__m256i S, __mmask16 U, __m256i A, __m256i B, const int I)

VPSHLDW ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_mask_shrdi_epi16 __m256i _mm256_mask_shrdi_epi16(__m256i S, __mmask16 U, __m256i A, __m256i B, const int I)

VPSHLDW ymm {k}, ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512vbmi2

_mm256_maskz_shldi_epi16 __m256i _mm256_maskz_shldi_epi16(__mmask16 U, __m256i A, __m256i B, const int I)

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

_mm256_maskz_shrdi_epi16 __m256i _mm256_maskz_shrdi_epi16(__mmask16 U, __m256i A, __m256i B, const int I)

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

_mm512_shldi_epi16 __m512i _mm512_shldi_epi16(__m512i A, __m512i B, const int I)

VPSHLDW zmm, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_shrdi_epi16 __m512i _mm512_shrdi_epi16(__m512i A, __m512i B, const int I)

VPSHLDW zmm, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_mask_shldi_epi16 __m512i _mm512_mask_shldi_epi16(__m512i S, __mmask32 U, __m512i A, __m512i B, const int I)

VPSHLDW zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_mask_shrdi_epi16 __m512i _mm512_mask_shrdi_epi16(__m512i S, __mmask32 U, __m512i A, __m512i B, const int I)

VPSHLDW zmm {k}, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_maskz_shldi_epi16 __m512i _mm512_maskz_shldi_epi16(__mmask32 U, __m512i A, __m512i B, const int I)

VPSHLDW zmm {k}{z}, zmm, zmm, imm8 EVEX.512 -mavx512vbmi2

_mm512_maskz_shrdi_epi16 __m512i _mm512_maskz_shrdi_epi16(__mmask32 U, __m512i A, __m512i B, const int I)

VPSHLDW zmm {k}{z}, zmm, zmm, imm8 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-622 (VPSHLD)
  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.