Extensions
Forms
4 (4 Legacy)
Data
Intel XED v2026.08.23

PHSUBW subtracts within neighboring pairs of words, the upper word of each pair from the lower one, and keeps the low 16 bits of each difference: the destination’s pairs fill the low half of the result and the source’s the high half, as PHADDW lays out its sums. Nothing saturates and no flag is set; PHSUBSW is the clamping form. The recorded Zen 5 case phsubw xmm7, xmmword ptr [mem] shows both the order and the wrap: the pair 000Fh, 0010h gave FFFFh (15 - 16), and 7FFFh, 8000h also gave FFFFh, the low bits of 32767 - (-32768) = 65535, where PHSUBSW would have returned 7FFFh. In the memory half, FFFFh, 8000h gave 7FFFh. Bits 511:128 of XMM7 stayed as they were (see mixing SSE and AVX).

In compiled code

In our builds at -O2 over fixed-size int16_t arrays, Clang 23 compiles o[i] = a[2*i] - a[2*i+1] to one PHSUBW per eight results with -mssse3, and to VPHSUBW and a VPERMQ that puts the 128-bit lanes in order with -mavx2. GCC 14 separates the even and odd words, with PSHUFB and POR or with masks, shifts and PACKUSDW, and subtracts them with PSUBW, as it does for the sums. The intrinsic _mm_hsub_epi16 is PHSUBW in both.

AMD’s latency spreadsheet for Zen 5 gives PHSUBW, like PHADDW, four macro-ops with a latency of two cycles and one started every two cycles. The MMX form came with SSSE3 too, and the XMM form’s memory operand must be aligned to 16 bytes.

Forms

Every encoding of PHSUBW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
PHSUBW mm, m64 PHSUBW_MMXq_MEMqNP 0F 38 05 /rSSSE3 + MMX
PHSUBW mm, mm PHSUBW_MMXq_MMXqNP 0F 38 05 /rSSSE3 + MMX
PHSUBW xmm, m128 PHSUBW_XMMdq_MEMdq66 0F 38 05 /rSSSE3
PHSUBW xmm, xmm PHSUBW_XMMdq_XMMdq66 0F 38 05 /rSSSE3

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.

Horizontal: adjacent pairs of words are combined, those of xmm1 into the low half of the result and those of xmm2 into the high half.
PHSUBW: adjacent pairsResult words 7 to 0: b6-b7, b4-b5, b2-b3, b0-b1, a6-a7, a4-a5, a2-a3, a0-a1.01234567xmm1aa0-a1a2-a3a4-a5a6-a7b0-b1b2-b3b4-b5b6-b7xmm101234567xmm2or m128b

Result words 7 to 0: b6-b7, b4-b5, b2-b3, b0-b1, a6-a7, a4-a5, a2-a3, a0-a1.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

PHSUBW mm, mm/m64
src1 = mm1.read()  # mm1 as it was
for i in range(4):
    j = 2 * (i % 2)
    if i < 2:
        mm1.w[i] = src1.w[j] - src1.w[j + 1]
    else:
        mm1.w[i] = src2.w[j] - src2.w[j + 1]
# x87: TOP = 0, all tags valid, bits 79:64 of mm1's register all ones

Run on AMD Zen 5 (EPYC 9645): 2 cases.

PHSUBW xmm, xmm/m128
src1 = xmm1.read()  # xmm1 as it was
for i in range(8):
    j = 2 * (i % 4)
    if i < 4:
        a = src1.w[j]
        b = src1.w[j + 1]
        xmm1.w[i] = a - b
    else:
        a = src2.w[j]
        b = src2.w[j + 1]
        xmm1.w[i] = a - b
# bits 128 and up of the register are unchanged

Run on AMD Zen 5 (EPYC 9645): 2 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
PHSUBW mm, mm/m64
mmexplicitread, write
mm/m64explicitread
PHSUBW xmm, xmm/m128
xmmexplicitread, write
xmm/m128explicitread

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.

PHSUBW mm, mm/m64
mmx-mem
PHSUBW xmm, xmm/m128
SSE_TYPE_4

Attributes

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

PHSUBW mm, mm/m64
may abort a TSX transaction
PHSUBW xmm, m128
aligned memory operand

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to PHSUBW, 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_hsub_epi16 __m128i _mm_hsub_epi16(__m128i __a, __m128i __b)

PHSUBW xmm, xmm Legacy -mssse3

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.

More SSSE3 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. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-302 (PHSUBW/PHSUBD)
  5. 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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.