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

VUNPCKHPS interleaves the high singles of two sources, (a2, b2, a3, b3), the VEX and EVEX form of UNPCKHPS, whose page shows how compilers use it to bring the upper half down. It adds a separate destination, memory at any alignment and zeroing above the vector length; the ymm and zmm forms work in each 128-bit lane, so the ymm form gives (a2, b2, a3, b3, a6, b6, a7, b7), and the memory form reads bytes 8 to 15 of each 16. VUNPCKLPS explains the lanes, the encodings and the code that pairs the two. The VEX forms need AVX, the EVEX forms AVX-512F (with AVX512VL below 512 bits) or AVX10.1, which add masking and a broadcast single.

Zen 5’s recorded cases:

  • vunpckhps ymm0, ymm13, ymmword ptr [mem] filled the low lane from elements 2 and 3 of YMM13 and of memory, and the high lane from elements 6 and 7.
  • vunpckhps ymm5{k6}{z}, ymm5, ymm5, one register as both sources, doubled each high single of a lane but wrote only elements 2, 5 and 7, which k6 selects: the copies of elements 3, 6 and 7. The other five were zeroed.
  • vunpckhps xmm5{k7}{z}, xmm5, dword bcst [mem] wrote element 2 of XMM5 and the single from memory into elements 0 and 1 and zeroed 2 and 3, k7’s clear bits.

In compiled code

In our builds at -O2 with -march=x86-64-v3, the loops that interleave two float arrays use VUNPCKHPS for the upper pairs of each lane beside VUNPCKLPS, in GCC 14 and Clang 23 alike. For the total of a __m256 kept in C’s order, GCC takes element 2 of each half with vunpckhps xmm, xmm, xmm of one register and Clang uses VSHUFPD. _mm256_unpackhi_ps is one VUNPCKHPS.

AMD’s latency spreadsheet for Zen 5 lists it like VUNPCKLPS: one macro-op of 1 cycle, four per cycle, in the VEX and the EVEX rows.

Forms

Every encoding of VUNPCKHPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VUNPCKHPS xmm, xmm, m128 VUNPCKHPS_XMMdq_XMMdq_MEMdqVEX.128.NP.0F.WIG 15 /rAVX
VUNPCKHPS xmm, xmm, xmm VUNPCKHPS_XMMdq_XMMdq_XMMdqVEX.128.NP.0F.WIG 15 /rAVX
VUNPCKHPS ymm, ymm, m256 VUNPCKHPS_YMMqq_YMMqq_MEMqqVEX.256.NP.0F.WIG 15 /rAVX
VUNPCKHPS ymm, ymm, ymm VUNPCKHPS_YMMqq_YMMqq_YMMqqVEX.256.NP.0F.WIG 15 /rAVX
VUNPCKHPS zmm {k}{z}, zmm, zmm VUNPCKHPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.NP.0F.W0 15 /rAVX10.1 or AVX512F
VUNPCKHPS zmm {k}{z}, zmm, m512/m32bcst VUNPCKHPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512EVEX.512.NP.0F.W0 15 /rAVX10.1 or AVX512F
VUNPCKHPS xmm {k}{z}, xmm, xmm VUNPCKHPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.NP.0F.W0 15 /rAVX10.1 or AVX512F + AVX512VL
VUNPCKHPS xmm {k}{z}, xmm, m128/m32bcst VUNPCKHPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.128.NP.0F.W0 15 /rAVX10.1 or AVX512F + AVX512VL
VUNPCKHPS ymm {k}{z}, ymm, ymm VUNPCKHPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.NP.0F.W0 15 /rAVX10.1 or AVX512F + AVX512VL
VUNPCKHPS ymm {k}{z}, ymm, m256/m32bcst VUNPCKHPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512EVEX.256.NP.0F.W0 15 /rAVX10.1 or AVX512F + AVX512VL

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, m128/m32bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m32bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m32bcst
Sandy Bridge, Haswell, Skylake7 / 1p51 / 1p58 / 1p51 / 1p5
Broadwell6 / 1p51 / 1p57 / 1p51 / 1p5
Skylake-SP, Ice Lake7 / 1p51 / 1p58 / 1p51 / 1p51 / 1p58 / 1p5
Alder Lake8 / 1p51 / 1p59 / 1p51 / 1p5
Sapphire Rapids8 / 1p51 / 1p59 / 1p51 / 1p51 / 1p59 / 1p5
Lunar Lake8 / 0.5V2 V31 / 0.5V2 V38 / 2.33V2 V31 / 0.5V2 V3
Piledriver7 / 1.5FPFMA FPU0 FPU12 / 1FPFMA FPU0 FPU17 / 2FPFMA FPU0 FPU12 / 2FPFMA FPU0 FPU1
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 / 1FP1 FP28 / 1FP1 FP2
Jaguar6 / 1FPA FPM FPU0 FPU11 / 0.5FPA FPM FPU0 FPU16 / 2FPA FPM FPU0 FPU11 / 1FPA FPM FPU0 FPU1

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 singles of both sources alternate in the result, those of xmm2 in the even places.
VUNPCKHPS: high halves interleavedResult singles 3 to 0: b3, unchanged (bit 2 of k1 is 0), b2, a2.0123xmm2a1110k1a2b2b3xmm10123xmm3or 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}. With m32bcst, one single from memory stands for every element of xmm3.

Result singles 3 to 0: b3, unchanged (bit 2 of k1 is 0), b2, a2.

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):
    j = i - i % 4 + i % 4 // 2 + 2  # in the lane of i
    if k1[i]:                       # 1 without a write mask
        if i % 2 == 0:
            zmm1.d[i] = zmm2.d[j]
        else:
            zmm1.d[i] = src3.d[j]
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src3.f32[i] is the m32 for every i
# 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
VUNPCKHPS xmm, xmm, xmm/m128 VUNPCKHPS ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VUNPCKHPS xmm {k}{z}, xmm, xmm/m128/m32bcst VUNPCKHPS ymm {k}{z}, ymm, ymm/m256/m32bcst VUNPCKHPS zmm {k}{z}, zmm, zmm/m512/m32bcst
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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
EVEX memory forms
embedded broadcast (tuple Full)

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VUNPCKHPS, 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_ps __m128 _mm_unpackhi_ps(__m128 __a, __m128 __b)

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

_mm_mask_unpackhi_ps __m128 _mm_mask_unpackhi_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B)

VUNPCKHPS xmm {k}, xmm, xmm EVEX.128 -mavx512vl

_mm_maskz_unpackhi_ps __m128 _mm_maskz_unpackhi_ps(__mmask8 __U, __m128 __A, __m128 __B)

VUNPCKHPS xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl

_mm256_unpackhi_ps __m256 _mm256_unpackhi_ps(__m256 __a, __m256 __b)

VUNPCKHPS ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_unpackhi_ps __m256 _mm256_mask_unpackhi_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B)

VUNPCKHPS ymm {k}, ymm, ymm EVEX.256 -mavx512vl

_mm256_maskz_unpackhi_ps __m256 _mm256_maskz_unpackhi_ps(__mmask8 __U, __m256 __A, __m256 __B)

VUNPCKHPS ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm512_unpackhi_ps __m512 _mm512_unpackhi_ps(__m512 __a, __m512 __b)

VUNPCKHPS zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_unpackhi_ps __m512 _mm512_mask_unpackhi_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B)

VUNPCKHPS zmm {k}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_unpackhi_ps __m512 _mm512_maskz_unpackhi_ps(__mmask16 __U, __m512 __A, __m512 __B)

VUNPCKHPS zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

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
AVX512F_512

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

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

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, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512F_128

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

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
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
AVX512F_256
Same as AVX512F_128Same as AVX512F_128

More AVX instructions

All 253 AVX 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-748 (UNPCKHPS)
  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. 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.