Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VPUNPCKHWD interleaves the high words of its two sources, a word of the first, a word of the second, and so on: the VEX and EVEX form of PUNPCKHWD, whose page covers the pairings with a zeroed register, with itself and with the high halves of products. VPUNPCKLBW covers what the newer encodings bring; the EVEX forms need AVX512BW (or AVX10.1) and take a write mask per word. Each 128-bit lane takes its own high four words: on Zen 5, vpunpckhwd ymm7, ymm11, ymmword ptr [mem] filled words 8 to 15 of the result from words 12 to 15 of each source, ECDFh from YMM11 and 884Dh from memory first.

Two halves of a doubleword

Interleaving puts each word of the first source in the low half of a doubleword and the matching word of the second source in the high half. Intel’s optimization manual converts half-precision values to single precision in AVX-128 code that way: it computes the upper and the lower 16 bits of each single in separate registers and joins them with VPUNPCKLWD and VPUNPCKHWD, the conversion that VCVTPH2PS does about 2.5 times as fast (Section 15.14.2, Example 15-33). With zero as the first source, each word lands in the upper half alone, which turns BF16 bits into the single of the same value: _mm256_unpackhi_epi16(_mm256_setzero_si256(), x) stays VPXOR and VPUNPCKHWD in GCC 14 and Clang 23 at -O2, while a loop of (uint32_t)h[i] << 16 compiles to VPMOVZXWD and VPSLLD in both.

In compiled code

In our builds with -march=x86-64-v3, interleaving two int16_t arrays is VPUNPCKLWD and VPUNPCKHWD of the same two registers in both compilers, followed by two VPERM2I128 in GCC and a VPERM2I128 and a VINSERTI128 in Clang, which put the lanes’ halves in order; with -march=x86-64-v4 both use VPERMT2W instead. AMD’s latency spreadsheet for Zen 5 gives the VEX and EVEX rows alike one cycle and four per cycle.

Forms

Every encoding of VPUNPCKHWD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPUNPCKHWD xmm, xmm, m128 VPUNPCKHWD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG 69 /rAVX
VPUNPCKHWD xmm, xmm, xmm VPUNPCKHWD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG 69 /rAVX
VPUNPCKHWD ymm, ymm, m256 VPUNPCKHWD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG 69 /rAVX2
VPUNPCKHWD ymm, ymm, ymm VPUNPCKHWD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG 69 /rAVX2
VPUNPCKHWD xmm {k}{z}, xmm, xmm VPUNPCKHWD_XMMu16_MASKmskw_XMMu16_XMMu16_AVX512EVEX.128.66.0F.WIG 69 /rAVX10.1 or AVX512BW + AVX512VL
VPUNPCKHWD xmm {k}{z}, xmm, m128 VPUNPCKHWD_XMMu16_MASKmskw_XMMu16_MEMu16_AVX512EVEX.128.66.0F.WIG 69 /rAVX10.1 or AVX512BW + AVX512VL
VPUNPCKHWD ymm {k}{z}, ymm, ymm VPUNPCKHWD_YMMu16_MASKmskw_YMMu16_YMMu16_AVX512EVEX.256.66.0F.WIG 69 /rAVX10.1 or AVX512BW + AVX512VL
VPUNPCKHWD ymm {k}{z}, ymm, m256 VPUNPCKHWD_YMMu16_MASKmskw_YMMu16_MEMu16_AVX512EVEX.256.66.0F.WIG 69 /rAVX10.1 or AVX512BW + AVX512VL
VPUNPCKHWD zmm {k}{z}, zmm, zmm VPUNPCKHWD_ZMMu16_MASKmskw_ZMMu16_ZMMu16_AVX512EVEX.512.66.0F.WIG 69 /rAVX10.1 or AVX512BW
VPUNPCKHWD zmm {k}{z}, zmm, m512 VPUNPCKHWD_ZMMu16_MASKmskw_ZMMu16_MEMu16_AVX512EVEX.512.66.0F.WIG 69 /rAVX10.1 or AVX512BW

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, xmm, m128
xmm {k}{z}, xmm, m128no mask
xmm, xmm, xmm
xmm {k}{z}, xmm, xmmno mask
ymm {k}{z}, ymm, ymmno mask
ymm, ymm, m256
ymm {k}{z}, ymm, m256no mask
ymm, ymm, ymmxmm {k}{z}, xmm, xmmwith a mask, zeroing
ymm {k}{z}, ymm, ymmwith a mask, zeroing
xmm {k}{z}, xmm, m128with a mask, zeroingymm {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
Sandy Bridge7 / 0.5p151 / 0.5p15
Haswell, Skylake7 / 1p51 / 1p58 / 1p51 / 1p5
Broadwell6 / 1p51 / 1p57 / 1p51 / 1p5
Skylake-SP7 / 1p51 / 1p58 / 1p51 / 1p51 / 1p57 / 1p58 / 1p51 / 1p51 / 1p58 / 1p58 / 1p5
Ice Lake7 / 0.5p151 / 0.5p158 / 0.5p151 / 0.5p151 / 0.5p157 / 0.5p158 / 0.5p151 / 1p51 / 1p58 / 1p58 / 1p5
Alder Lake8 / 0.5p151 / 0.5p159 / 0.5p151 / 0.5p15
Sapphire Rapids8 / 0.5p151 / 0.5p159 / 0.5p151 / 0.5p153 / 0.5p1511 / 0.5p1511 / 0.5p151 / 1p53 / 1p59 / 1p511 / 1p5
Lunar Lake8 / 0.5V2 V31 / 0.5V2 V39 / 0.5V2 V31 / 0.5V2 V3
Piledriver7 / 1.5FPU1 FPXBR2 / 1FPU1 FPXBR
Zen8 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 1FPU1 FPU21 / 1FPU1 FPU2
Zen 28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU28 / 0.5FPU1 FPU21 / 0.5FPU1 FPU2
Zen 38 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP2
Zen 48 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP21 / 0.5FP1 FP21 / 0.5FP1 FP28 / 0.5FP1 FP28 / 0.5FP1 FP21 / 1FP1 FP21 / 1FP1 FP28 / 1FP1 FP28 / 1FP1 FP2
Jaguar6 / 1FPU0 FPU1 VALU0 VALU11 / 0.5FPU0 FPU1 VALU0 VALU1

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.

Interleave: the high words of both sources alternate in the result, those of xmm2 in the even places.
VPUNPCKHWD: high halves interleavedResult words 7 to 0: b7, unchanged (bit 6 of k1 is 0), b6, a6, b5, a5, b4, a4.01234567xmm2a11111110k1a4a5a6b4b5b6b7xmm101234567xmm3or m128b

The ymm and zmm forms repeat this in each 128-bit lane. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result words 7 to 0: b7, unchanged (bit 6 of k1 is 0), b6, a6, b5, a5, b4, a4.

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):
    j = i - i % 8 + i % 8 // 2 + 4  # in the lane of i
    if k1[i]:                       # 1 without a write mask
        if i % 2 == 0:
            zmm1.w[i] = zmm2.w[j]
        else:
            zmm1.w[i] = src3.w[j]
    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): 10 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
VPUNPCKHWD xmm, xmm, xmm/m128 VPUNPCKHWD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPUNPCKHWD xmm {k}{z}, xmm, xmm/m128 VPUNPCKHWD ymm {k}{z}, ymm, ymm/m256 VPUNPCKHWD zmm {k}{z}, zmm, zmm/m512
xmm, ymm, zmmexplicitwrite (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.

VEX forms
avx-type-4
EVEX forms
AVX512-E4NF

Attributes

What else XED records about the forms. How to read.

EVEX forms
write masking

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPUNPCKHWD, 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_unpackhi_epi16 __m128i _mm_unpackhi_epi16(__m128i __a, __m128i __b)

VPUNPCKHWD xmm, xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_unpackhi_epi16 __m128i _mm_mask_unpackhi_epi16(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B)

VPUNPCKHWD xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm_maskz_unpackhi_epi16 __m128i _mm_maskz_unpackhi_epi16(__mmask8 __U, __m128i __A, __m128i __B)

VPUNPCKHWD xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm256_unpackhi_epi16 __m256i _mm256_unpackhi_epi16(__m256i __a, __m256i __b)

VPUNPCKHWD ymm, ymm, ymm VEX.256 -mavx2

_mm256_mask_unpackhi_epi16 __m256i _mm256_mask_unpackhi_epi16(__m256i __W, __mmask16 __U, __m256i __A, __m256i __B)

VPUNPCKHWD ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm256_maskz_unpackhi_epi16 __m256i _mm256_maskz_unpackhi_epi16(__mmask16 __U, __m256i __A, __m256i __B)

VPUNPCKHWD ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm512_unpackhi_epi16 __m512i _mm512_unpackhi_epi16(__m512i __A, __m512i __B)

VPUNPCKHWD zmm, zmm, zmm EVEX.512 -mavx512bw

_mm512_mask_unpackhi_epi16 __m512i _mm512_mask_unpackhi_epi16(__m512i __W, __mmask32 __U, __m512i __A, __m512i __B)

VPUNPCKHWD zmm {k}, zmm, zmm EVEX.512 -mavx512bw

_mm512_maskz_unpackhi_epi16 __m512i _mm512_maskz_unpackhi_epi16(__mmask32 __U, __m512i __A, __m512i __B)

VPUNPCKHWD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512bw

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
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX2

AVX2
CPUID.(EAX=07H,ECX=0):EBX[5] AVX2

Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX512BW_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512BW_256
Same as AVX512BW_128Same as AVX512BW_128
AVX512BW_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW

Same as AVX512BW_128

More AVX instructions

All 253 AVX instructions

More AVX2 instructions

All 138 AVX2 instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-502 (PUNPCKHBW/PUNPCKHWD/PUNPCKHDQ/PUNPCKHQDQ)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  9. 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.