Extensions
Forms
2 (2 EVEX)
Data
Intel XED v2026.08.23

VFIXUPIMMSS is the scalar form of VFIXUPIMMPS, whose page has the classes, the codes and the immediate bits: it sorts the low single of its first source into one of eight classes, replaces the low single of the destination with the value that the class’s 4-bit code in the low doubleword of the second source names, and takes bits 127:32 from the first source. Code 0 keeps the destination, so a routine computes its result first and patches only the special inputs. VFIXUPIMMSD is the double-precision form. It came with AVX512F, with a write mask on the one element and {sae}.

Recorded on Zen 5

  • A large number. 543210FEh, an ordinary positive single, used as input and table, took code 5 and became +infinity, 7F800000h.
  • An SNaN. FF800001h with the table EDCBA987h took code 8 and gave +0; the immediate 55h, whose bit 4 makes an SNaN signal, set IE.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 compile _mm_fixupimm_ss to VFIXUPIMMSS; a constant mask with bit 0 set, as in _mm_maskz_fixupimm_ss(3, ...), is dropped.

AMD’s Zen 5 latency spreadsheet gives one macro-op on pipe FP0 or FP1 and 2 cycles.

Forms

Every encoding of VFIXUPIMMSS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VFIXUPIMMSS xmm {k}{z}, xmm, xmm, imm8, {sae} VFIXUPIMMSS_XMMf32_MASKmskw_XMMf32_XMMf32_IMM8_AVX512EVEX.LIG.66.0F3A.W0 55 /r ibAVX10.1 or AVX512F
VFIXUPIMMSS xmm {k}{z}, xmm, m32, imm8 VFIXUPIMMSS_XMMf32_MASKmskw_XMMf32_MEMf32_IMM8_AVX512EVEX.LIG.66.0F3A.W0 55 /r ibAVX10.1 or AVX512F

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 {k}{z}, xmm, xmm, imm8, {sae}no maskxmm {k}{z}, xmm, xmm, imm8, {sae}with a mask, zeroingxmm {k}{z}, xmm, xmm, imm8, {sae}with {sae}xmm {k}{z}, xmm, m32, imm8
Skylake-SP, Ice Lake4 / 0.5p014 / 0.5p019 / 0.5p01239 / 0.5p01
Sapphire Rapids4 / 0.5p014 / 0.5p014 / 0.5p0111 / 0.5p01
Zen 43 / 0.5FP2 FP32 / 1FP0 FP110 / 0.5FP2 FP3 FP45 LSU Load10 / 0.5FP2 FP3

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.

Scalar: only the low single is computed; the other singles come from xmm2.
VFIXUPIMMSS: the low elementResult single 0 is computed from single 0 of xmm1, xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: b3, b2, b1, r0.0123xmm1a1k1r0b1b2b3xmm10123xmm2b0123xmm3or m32c

The write mask k1 applies to the low single: with bit 0 clear it keeps its old value, or is zeroed with {z}.

Result single 0 is computed from single 0 of xmm1, xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: b3, b2, b1, r0.

Operation

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

if k1[0]:
    a = xmm1.f32[0]
    b = xmm2.f32[0]
    sc = src3.sd[0]
    xmm1.f32[0] = fixupimm(a, b, sc, imm8)
elif zeroing:
    xmm1.f32[0] = 0
# else: xmm1.f32[0] keeps its value
for i in range(1, 4):
    xmm1.d[i] = xmm2.d[i]
# {sae}: no exception flags
# sc: four bits for each class of b that name the result; imm8: the classes that raise ZE or IE
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 3 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
VFIXUPIMMSS xmm {k}{z}, xmm, xmm/m32, imm8, {sae}
xmmexplicitread, write (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m32explicitread
imm8explicitread

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
AVX512-E3

Attributes

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

All forms
write masking; follows MXCSR
Memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VFIXUPIMMSS, 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_fixupimm_round_ss __m128 _mm_fixupimm_round_ss(__m128 A, __m128 B, __m128i C, const int imm, const int R)

VFIXUPIMMSS xmm, xmm, xmm, imm8, {sae} EVEX.LIG -mavx512f

_mm_fixupimm_ss __m128 _mm_fixupimm_ss(__m128 A, __m128 B, __m128i C, const int imm)

VFIXUPIMMSS xmm, xmm, xmm, imm8 EVEX.LIG -mavx512f

_mm_mask_fixupimm_round_ss __m128 _mm_mask_fixupimm_round_ss(__m128 A, __mmask8 U, __m128 B, __m128i C, const int imm, const int R)

VFIXUPIMMSS xmm {k}, xmm, xmm, imm8, {sae} EVEX.LIG -mavx512f

_mm_mask_fixupimm_ss __m128 _mm_mask_fixupimm_ss(__m128 A, __mmask8 U, __m128 B, __m128i C, const int imm)

VFIXUPIMMSS xmm {k}, xmm, xmm, imm8 EVEX.LIG -mavx512f

_mm_maskz_fixupimm_round_ss __m128 _mm_maskz_fixupimm_round_ss(__mmask8 U, __m128 A, __m128 B, __m128i C, const int imm, const int R)

VFIXUPIMMSS xmm {k}{z}, xmm, xmm, imm8, {sae} EVEX.LIG -mavx512f

_mm_maskz_fixupimm_ss __m128 _mm_maskz_fixupimm_ss(__mmask8 U, __m128 A, __m128 B, __m128i C, const int imm)

VFIXUPIMMSS xmm {k}{z}, xmm, xmm, imm8 EVEX.LIG -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
AVX512F_SCALAR

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

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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-203 (VFIXUPIMMSS)
  7. 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.