Instruction
VUNPCKHPS
Interleaves the high singles of each 128-bit lane of two sources.
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
| Instruction | Encoding | Requires |
|---|---|---|
VUNPCKHPS xmm, xmm, m128
VUNPCKHPS_XMMdq_XMMdq_MEMdq | VEX.128.NP.0F.WIG 15 /r | AVX |
VUNPCKHPS xmm, xmm, xmm
VUNPCKHPS_XMMdq_XMMdq_XMMdq | VEX.128.NP.0F.WIG 15 /r | AVX |
VUNPCKHPS ymm, ymm, m256
VUNPCKHPS_YMMqq_YMMqq_MEMqq | VEX.256.NP.0F.WIG 15 /r | AVX |
VUNPCKHPS ymm, ymm, ymm
VUNPCKHPS_YMMqq_YMMqq_YMMqq | VEX.256.NP.0F.WIG 15 /r | AVX |
VUNPCKHPS zmm {k}{z}, zmm, zmm
VUNPCKHPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512 | EVEX.512.NP.0F.W0 15 /r | AVX10.1 or AVX512F |
VUNPCKHPS zmm {k}{z}, zmm, m512/m32bcst
VUNPCKHPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512 | EVEX.512.NP.0F.W0 15 /r | AVX10.1 or AVX512F |
VUNPCKHPS xmm {k}{z}, xmm, xmm
VUNPCKHPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.128.NP.0F.W0 15 /r | AVX10.1 or AVX512F + AVX512VL |
VUNPCKHPS xmm {k}{z}, xmm, m128/m32bcst
VUNPCKHPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512 | EVEX.128.NP.0F.W0 15 /r | AVX10.1 or AVX512F + AVX512VL |
VUNPCKHPS ymm {k}{z}, ymm, ymm
VUNPCKHPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512 | EVEX.256.NP.0F.W0 15 /r | AVX10.1 or AVX512F + AVX512VL |
VUNPCKHPS ymm {k}{z}, ymm, m256/m32bcst
VUNPCKHPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512 | EVEX.256.NP.0F.W0 15 /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m32bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m32bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|
| Sandy Bridge, Haswell, Skylake | 7 / 1p5 | 1 / 1p5 | 8 / 1p5 | 1 / 1p5 | ||
| Broadwell | 6 / 1p5 | 1 / 1p5 | 7 / 1p5 | 1 / 1p5 | ||
| Skylake-SP, Ice Lake | 7 / 1p5 | 1 / 1p5 | 8 / 1p5 | 1 / 1p5 | 1 / 1p5 | 8 / 1p5 |
| Alder Lake | 8 / 1p5 | 1 / 1p5 | 9 / 1p5 | 1 / 1p5 | ||
| Sapphire Rapids | 8 / 1p5 | 1 / 1p5 | 9 / 1p5 | 1 / 1p5 | 1 / 1p5 | 9 / 1p5 |
| Lunar Lake | 8 / 0.5V2 V3 | 1 / 0.5V2 V3 | 8 / 2.33V2 V3 | 1 / 0.5V2 V3 | ||
| Piledriver | 7 / 1.5FPFMA FPU0 FPU1 | 2 / 1FPFMA FPU0 FPU1 | 7 / 2FPFMA FPU0 FPU1 | 2 / 2FPFMA FPU0 FPU1 | ||
| Zen | 8 / 0.5FPU1 FPU2 | 1 / 0.5FPU1 FPU2 | 8 / 1FPU1 FPU2 | 1 / 1FPU1 FPU2 | ||
| Zen 2 | 8 / 0.5FPU1 FPU2 | 1 / 0.5FPU1 FPU2 | 8 / 0.5FPU1 FPU2 | 1 / 0.5FPU1 FPU2 | ||
| Zen 3 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | ||
| Zen 4 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 1 / 1FP1 FP2 | 8 / 1FP1 FP2 |
| Jaguar | 6 / 1FPA FPM FPU0 FPU1 | 1 / 0.5FPA FPM FPU0 FPU1 | 6 / 2FPA FPM FPU0 FPU1 | 1 / 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.
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 upRun on AMD Zen 5 (EPYC 9645): 10 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VUNPCKHPS xmm, xmm, xmm/m128 VUNPCKHPS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
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, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | explicit | read |
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.
| Intrinsic | Compiles to |
|---|---|
_mm_unpackhi_ps
__m128 _mm_unpackhi_ps(__m128 __a, __m128 __b) |
|
_mm_mask_unpackhi_ps
__m128 _mm_mask_unpackhi_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B) |
|
_mm_maskz_unpackhi_ps
__m128 _mm_maskz_unpackhi_ps(__mmask8 __U, __m128 __A, __m128 __B) |
|
_mm256_unpackhi_ps
__m256 _mm256_unpackhi_ps(__m256 __a, __m256 __b) |
|
_mm256_mask_unpackhi_ps
__m256 _mm256_mask_unpackhi_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B) |
|
_mm256_maskz_unpackhi_ps
__m256 _mm256_maskz_unpackhi_ps(__mmask8 __U, __m256 __A, __m256 __B) |
|
_mm512_unpackhi_ps
__m512 _mm512_unpackhi_ps(__m512 __a, __m512 __b) |
|
_mm512_mask_unpackhi_ps
__m512 _mm512_mask_unpackhi_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_maskz_unpackhi_ps
__m512 _mm512_maskz_unpackhi_ps(__mmask16 __U, __m512 __A, __m512 __B) |
|
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.
More AVX instructions
- VPTEST
- VPUNPCKHBW
- VPUNPCKHDQ
- VPUNPCKHQDQ
- VPUNPCKHWD
- VPUNPCKLBW
- VPUNPCKLDQ
- VPUNPCKLQDQ
- VPUNPCKLWD
- VPXOR
- VRCPPS
- VRCPSS
- VROUNDPD
- VROUNDPS
- VROUNDSD
- VROUNDSS
- VRSQRTPS
- VRSQRTSS
- VSHUFPD
- VSHUFPS
- VSQRTPD
- VSQRTPS
- VSQRTSD
- VSQRTSS
- VSTMXCSR
- VSUBPD
- VSUBPS
- VSUBSD
- VSUBSS
- VTESTPD
- VTESTPS
- VUCOMISD
- VUCOMISS
- VUNPCKHPD
- VUNPCKLPD
- VUNPCKLPS
- VXORPD
- VXORPS
- VZEROALL
- VZEROUPPER
More AVX10.1 instructions
- VRSQRT14SD
- VRSQRT14SS
- VRSQRTPH
- VRSQRTSH
- VSCALEFPD
- VSCALEFPH
- VSCALEFPS
- VSCALEFSD
- VSCALEFSH
- VSCALEFSS
- VSCATTERDPD
- VSCATTERDPS
- VSCATTERQPD
- VSCATTERQPS
- VSHUFF32X4
- VSHUFF64X2
- VSHUFI32X4
- VSHUFI64X2
- VSHUFPD
- VSHUFPS
- VSQRTPD
- VSQRTPH
- VSQRTPS
- VSQRTSD
- VSQRTSH
- VSQRTSS
- VSUBPD
- VSUBPH
- VSUBPS
- VSUBSD
- VSUBSH
- VSUBSS
- VUCOMISD
- VUCOMISH
- VUCOMISS
- VUNPCKHPD
- VUNPCKLPD
- VUNPCKLPS
- VXORPD
- VXORPS
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-748 (UNPCKHPS)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- 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.