VPSIGNB instruction (AVX, AVX2)

Forms

Every encoding of VPSIGNB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.

Instruction	Encoding	Requires
`VPSIGNB xmm, xmm, m128` VPSIGNB_XMMdq_XMMdq_MEMdq	`VEX.128.66.0F38.WIG 08 /r`	AVX
`VPSIGNB xmm, xmm, xmm` VPSIGNB_XMMdq_XMMdq_XMMdq	`VEX.128.66.0F38.WIG 08 /r`	AVX
`VPSIGNB ymm, ymm, m256` VPSIGNB_YMMqq_YMMqq_MEMqq	`VEX.256.66.0F38.WIG 08 /r`	AVX2
`VPSIGNB ymm, ymm, ymm` VPSIGNB_YMMqq_YMMqq_YMMqq	`VEX.256.66.0F38.WIG 08 /r`	AVX2

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 byte of the result comes from the byte in the same place in each source.

Shown: bytes 7 to 0. Every byte works alike: 16 and 32 bytes in the xmm and ymm forms.

Result byte i comes from byte i of xmm2 and xmm3. Result bytes 7 to 0: r7, r6, r5, r4, r3, r2, r1, r0.

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 // 8):
    a = ymm2.b[i]
    b = src3.b[i]
    sb = src3.sb[i]
    if sb < 0:
        ymm1.b[i] = -a
    elif b == 0:
        ymm1.b[i] = 0
    else:
        ymm1.b[i] = a
# ymm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 4 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.

Operand	Kind	Action
`VPSIGNB xmm, xmm, xmm/m128` `VPSIGNB ymm, ymm, ymm/m256`
`xmm, ymm`	explicit	write
`xmm, ymm`	explicit	read
`xmm/m128, ymm/m256`	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.

All forms: avx-type-4

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSIGNB, 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_sign_epi8` `__m128i _mm_sign_epi8(__m128i __a, __m128i __b)`	`VPSIGNB xmm, xmm, xmm` VEX.128 -mavxwith AVX enabled
`_mm256_sign_epi8` `__m256i _mm256_sign_epi8(__m256i __a, __m256i __b)`	`VPSIGNB ymm, ymm, ymm` VEX.256 -mavx2

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 set	CPUID	Processors
`AVX` 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	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

More AVX instructions

All 253 AVX instructions

More AVX2 instructions

All 138 AVX2 instructions