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

VPSHRDVQ is the quadword form of VPSHRDVD: per element, the quadword of the first source is joined above the destination’s, the 128-bit pair is shifted right by the count in the matching quadword of the second source, taken modulo 64, and the low 64 bits are written back to the destination. VPSHRDVD’s page explains why the destination is the lower half, and VPSHRDQ is the form with one immediate count. It belongs to AVX512_VBMI2, which -march=znver5 enables and x86-64-v4 does not.

Recorded on Zen 5

  • A funnel. {evex} vpshrdvq xmm14, xmm8, xmm29 shifted 0 under 1 right by one: element 1 became 8000000000000000h, bit 0 of the first source moved into bit 63.
  • Counts modulo 64. A count of 7FFFFFFFFFFFFFFFh acted as 63: with 8 in both halves, vpshrdvq ymm5{k2}, ymm5, ymmword ptr [mem] gave 10h, and a count of 8000000000000000h acted as 0 and left the element as it was.
  • One register three times is a rotate right by the element itself: in vpshrdvq zmm5{k4}, zmm5, zmm5, 7Fh became FEh, a rotate right by 63, and 1 became 8000000000000000h.

In compiled code

At -O2 with -march=znver5, Clang 23 compiles s ? (lo[i] >> s) | (hi[i] << (64 - s)) : lo[i] with uint64_t s = c[i] & 63 to VPSHRDVQ on ZMM registers, keeping a test of s against zero with VPTESTNMQ, and the branch-free (lo[i] >> s) | ((hi[i] << 1) << (63 - s)) to VPSHRDVQ alone. With a 32-bit s it keeps the plain shifts, and GCC 14 does in every case, with VPSRLVQ, VPSLLVQ and an OR. _mm512_shrdv_epi64(a, b, c) is one VPSHRDVQ in both, a the lower half and the register written.

AMD’s Zen 5 latency spreadsheet gives one macro-op, 2 cycles, two per cycle on pipes FP0 and FP1, as for VPSHRDQ.

Forms

Every encoding of VPSHRDVQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSHRDVQ xmm {k}{z}, xmm, xmm VPSHRDVQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F38.W1 73 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVQ xmm {k}{z}, xmm, m128/m64bcst VPSHRDVQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F38.W1 73 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVQ ymm {k}{z}, ymm, ymm VPSHRDVQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F38.W1 73 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVQ ymm {k}{z}, ymm, m256/m64bcst VPSHRDVQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F38.W1 73 /rAVX10.1 or AVX512_VBMI2 + AVX512VL
VPSHRDVQ zmm {k}{z}, zmm, zmm VPSHRDVQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F38.W1 73 /rAVX10.1 or AVX512_VBMI2
VPSHRDVQ zmm {k}{z}, zmm, m512/m64bcst VPSHRDVQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F38.W1 73 /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, m128/m64bcstymm {k}{z}, ymm, m256/m64bcstzmm {k}{z}, zmm, zmmno maskzmm {k}{z}, zmm, zmmwith a mask, zeroingzmm {k}{z}, zmm, m512/m64bcst
Ice Lake5 / 0.5p015 / 0.5p0111 / 0.5p0112 / 0.5p015 / 0.5p055 / 0.5p0512 / 0.5p05
Sapphire Rapids1 / 0.5p011 / 0.5p018 / 0.5p019 / 0.5p011 / 1p01 / 1p09 / 1p0
Zen 43 / 0.5FP0 FP32 / 1FP0 FP110 / 0.5FP0 FP310 / 0.5FP0 FP33 / 1FP0 FP32 / 1FP0 FP110 / 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.
VPSHRDVQ: element by elementResult quadword i comes from quadword i of xmm1, xmm2 and xmm3. Result quadwords 1 to 0: r1, r0.01xmm1a01xmm2b01xmm3or m128c11k1r0r1xmm1

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. The sources are drawn above the result, each element in its own column.

Result quadword i comes from quadword i of xmm1, 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 = zmm1.q[i]
        b = zmm2.q[i]
        c = src3.q[i]
        x = b << 64 | a
        zmm1.q[i] = x >> (c & 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
VPSHRDVQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPSHRDVQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPSHRDVQ zmm {k}{z}, zmm, zmm/m512/m64bcst
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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 VPSHRDVQ, 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_epi64 __m128i _mm_shrdv_epi64(__m128i __A, __m128i __B, __m128i __C)

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

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

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

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

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

_mm256_shrdv_epi64 __m256i _mm256_shrdv_epi64(__m256i __A, __m256i __B, __m256i __C)

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

_mm256_mask_shrdv_epi64 __m256i _mm256_mask_shrdv_epi64(__m256i __A, __mmask8 __U, __m256i __B, __m256i __C)

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

_mm256_maskz_shrdv_epi64 __m256i _mm256_maskz_shrdv_epi64(__mmask8 __U, __m256i __A, __m256i __B, __m256i __C)

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

_mm512_shrdv_epi64 __m512i _mm512_shrdv_epi64(__m512i __A, __m512i __B, __m512i __C)

VPSHRDVQ zmm, zmm, zmm EVEX.512 -mavx512vbmi2

_mm512_mask_shrdv_epi64 __m512i _mm512_mask_shrdv_epi64(__m512i __A, __mmask8 __U, __m512i __B, __m512i __C)

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

_mm512_maskz_shrdv_epi64 __m512i _mm512_maskz_shrdv_epi64(__mmask8 __U, __m512i __A, __m512i __B, __m512i __C)

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