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

PSIGND applies the sign of each source doubleword to the matching destination doubleword: negated for a negative source, cleared for zero, unchanged for a positive one, four elements in an XMM register and two in an MMX one. PSIGNB covers the family and its SSSE3 history. The negation wraps: on Zen 5, the recorded psignd xmm0, xmmword ptr [mem] left 80000000h as 80000000h where the source element was negative, as PABSD does with the same value, and kept 7FFFFFFFh and 0000000Fh under positive source elements; it left bits 511:128 of XMM0 as they were (see mixing SSE and AVX).

In compiled code

In our builds at -O2 with -mssse3, neither GCC 14 nor Clang 23 derives PSIGND from C, and both keep it exactly as written when it comes from _mm_sign_epi32:

  • _mm_sign_epi32(x, x) stays PSIGND, not PABSD, and _mm_sign_epi32(x, _mm_set1_epi32(-1)) becomes PCMPEQD and PSIGND, where a negation would otherwise be a PSUBD from zero.
  • A two-way conditional negation, e[i] < 0 ? -d[i] : d[i] over int32_t arrays, is a sign mask from PCMPGTD in both; Clang applies it with PXOR and PSUBD, GCC selects between the value and its negation with PAND, PANDN and POR.
  • Multiplying by the sign, d[i] * ((e[i] > 0) - (e[i] < 0)), stays a multiplication: two PCMPGTD and a PSUBD build -1, 0 or 1, then PMULUDQ pairs, or VPMULLD with -mavx2.

AMD’s latency spreadsheet for Zen 5 gives PSIGND one macro-op with a latency of two cycles and two per cycle, on pipes FP0 and FP3, the same as PSIGNB and PSIGNW. The XMM form’s memory operand must be aligned to 16 bytes; VPSIGND is the VEX form, and AVX-512 has no sign instructions.

Forms

Every encoding of PSIGND that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
PSIGND mm, m64 PSIGND_MMXq_MEMqNP 0F 38 0A /rSSSE3 + MMX
PSIGND mm, mm PSIGND_MMXq_MMXqNP 0F 38 0A /rSSSE3 + MMX
PSIGND xmm, m128 PSIGND_XMMdq_MEMdq66 0F 38 0A /rSSSE3
PSIGND xmm, xmm PSIGND_XMMdq_XMMdq66 0F 38 0A /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.

Element-wise: each doubleword of the result comes from the doubleword in the same place in each source.
PSIGND: element by elementResult doubleword i comes from doubleword i of xmm1 and xmm2. Result doublewords 3 to 0: r3, r2, r1, r0.0123xmm1ar0r1r2r3xmm10123xmm2or m128b

Every doubleword works alike: 2 and 4 doublewords in the mm and xmm forms.

Result doubleword i comes from doubleword i of xmm1 and xmm2. Result doublewords 3 to 0: r3, r2, r1, r0.

Operation

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

PSIGND mm, mm/m64
for i in range(2):
    a = mm1.d[i]
    b = src2.d[i]
    sb = src2.sd[i]
    if sb < 0:
        mm1.d[i] = -a
    elif b == 0:
        mm1.d[i] = 0
    else:
        mm1.d[i] = a
# x87: TOP = 0, all tags valid, bits 79:64 of mm1's register all ones

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

PSIGND xmm, xmm/m128
for i in range(4):
    a = xmm1.d[i]
    b = src2.d[i]
    sb = src2.sd[i]
    if sb < 0:
        xmm1.d[i] = -a
    elif b == 0:
        xmm1.d[i] = 0
    else:
        xmm1.d[i] = a
# 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
PSIGND mm, mm/m64
mmexplicitread, write
mm/m64explicitread
PSIGND 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.

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

Attributes

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

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

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to PSIGND, 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_sign_epi32 __m128i _mm_sign_epi32(__m128i __a, __m128i __b)

PSIGND 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-437 (PSIGNB/PSIGNW/PSIGND)
  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.