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

VCMPSS is the VEX and EVEX form of CMPSS, whose page covers the scalar compare and when compilers prefer it to the flags of COMISS. It compares the low singles of its two sources under the 32 predicates of VCMPPS, chosen by bits 4:0 of the immediate. The VEX form, for AVX, writes all ones or zero to the low single of a separate destination, copies singles 1 to 3 from the first source and clears the bits above 127. The EVEX form, for AVX-512F or AVX10.1, writes bit 0 of a mask register and clears the others; a write mask with bit 0 clear forces that bit to 0, and {sae} keeps the compare from reporting any exception.

Recorded on Zen 5

  • vcmpss xmm1, xmm2, xmm3, 0x4, not equal and quiet, compared a quiet NaN with a signaling one, wrote FFFFFFFFh and set MXCSR.IE: a quiet predicate does not cover a signaling NaN.
  • vcmpss xmm0, xmm13, dword ptr [mem], 0xd, greater or equal, found the single nearest 1.0E-30 equal to itself and kept -1.0, the NaN and 1.0 of XMM13 above it.
  • vcmpss k5{k6}, xmm0, xmm31, {sae}, 0x1c, with bit 0 of K6 clear, left K5 at 0 although the minimum normal single and 0.5 differ.

In compiled code

In our builds at -O2 with -march=x86-64-v3, a < b ? c : d over float is VCMPSS and a VBLENDVPS in GCC 14 and Clang 23, GCC again computing not-less-than with c and d swapped. With -march=x86-64-v4 GCC keeps that, while Clang compares into K1 and selects with a masked VMOVSS. The VEX predicates include greater-than, 0Eh, yet _mm_cmpgt_ss still swaps its operands as on CMPSS’s page: GCC with VCMPLTPS and VMOVSS, Clang with VCMPLTSS and VBLENDPS.

AMD’s latency spreadsheet for Zen 5 gives the VEX row 2 cycles on pipes FP2 and FP3, as for CMPSS, and the EVEX rows, which write a mask register, 3 cycles on FP1 and FP2, with a second macro-op for the memory form. VCMPSD is the double form.

Forms

Every encoding of VCMPSS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCMPSS xmm, xmm, m32, imm8 VCMPSS_XMMdq_XMMdq_MEMd_IMMbVEX.LIG.F3.0F.WIG C2 /r ibAVX
VCMPSS xmm, xmm, xmm, imm8 VCMPSS_XMMdq_XMMdq_XMMd_IMMbVEX.LIG.F3.0F.WIG C2 /r ibAVX
VCMPSS k {k}, xmm, xmm, imm8, {sae} VCMPSS_MASKmskw_MASKmskw_XMMf32_XMMf32_IMM8_AVX512EVEX.LIG.F3.0F.W0 C2 /r ibAVX10.1 or AVX512F
VCMPSS k {k}, xmm, m32, imm8 VCMPSS_MASKmskw_MASKmskw_XMMf32_MEMf32_IMM8_AVX512EVEX.LIG.F3.0F.W0 C2 /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, xmm, m32, imm8xmm, xmm, xmm, imm8k {k}, xmm, xmm, imm8, {sae}no mask, with a maskk {k}, xmm, xmm, imm8, {sae}with {sae}k {k}, xmm, m32, imm8
Sandy Bridge9 / 1p13 / 1p1
Haswell, Broadwell8 / 1p13 / 1p1
Skylake9 / 0.5p014 / 0.5p01
Skylake-SP, Ice Lake9 / 0.5p014 / 0.5p014 / 1p54 / 1p510 / 1p5
Alder Lake11 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 0.5p013 / 1p54 / 0.5p013 / 1p5
Lunar Lake10 / 2V0 V14 / 2V0 V1
Piledriver7 / 1.5FPFMA FPU02 / 1FPFMA FPU0
Zen, Zen 28 / 0.5FPU0 FPU11 / 0.5FPU0 FPU1
Zen 38 / 0.5FP0 FP11 / 0.5FP0 FP1
Zen 49 / 1FP0 FP12 / 1FP0 FP12 / 11FP0 FP12 / 11FP0 FP19 / 1FP0 FP1
Jaguar7 / 1FPA FPU02 / 1FPA FPU0
  1. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 955; AMD 58455, row 24).

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.VEX forms
VCMPSS: the low elementResult single 0 is computed from single 0 of xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, a1, r0.0123xmm2ar0a1a2a3xmm10123xmm3or m32b

Result single 0 is computed from single 0 of xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, a1, r0.

Only the low singles count: the result goes to bit 0 of k1, and its other bits are cleared.EVEX forms
VCMPSS: the low element to bit 0 of k1The result comes from single 0 of xmm2 and xmm3. Result bits 3 to 0: 0, 0, 0, r0.01231k2r00k10123xmm3or m32b

Where bit 0 of the write mask k2 is 0, the result bit is 0.

The result comes from single 0 of xmm2 and xmm3. Result bits 3 to 0: 0, 0, 0, r0.

Operation

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

VEX forms
a = xmm2.f32[0]
b = src3.f32[0]
xmm1.d[0] = -1 if fcmp(imm8, a, b) else 0
for i in range(1, 4):
    xmm1.d[i] = xmm2.d[i]
# imm8 & 31: 0 ==, 1 <, 2 <=, 3 unordered, 4 !=, 5 !<, 6 !<=, 7 ordered ...
# xmm1 is zeroed from bit 128 up

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

EVEX forms
a = xmm2.f32[0]
b = src3.f32[0]
k1[0] = k2[0] and fcmp(imm8, a, b)
# imm8 & 31: 0 ==, 1 <, 2 <=, 3 unordered, 4 !=, 5 !<, 6 !<=, 7 ordered ...
# {sae}: no exception flags
# the other bits of k1 are cleared

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
VCMPSS xmm, xmm, xmm/m32, imm8
xmmexplicitwrite
xmmexplicitread
xmm/m32explicitread
imm8explicitread
VCMPSS k {k}, xmm, xmm/m32, imm8, {sae}
kexplicitwrite (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.

VEX forms
avx-type-3
EVEX forms
AVX512-E3

Attributes

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

All forms
follows MXCSR
EVEX forms
write masking
EVEX memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCMPSS, 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_cmp_round_ss_mask __mmask8 _mm_cmp_round_ss_mask(__m128 X, __m128 Y, const int P, const int R)

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

_mm_cmp_ss_mask __mmask8 _mm_cmp_ss_mask(__m128 X, __m128 Y, const int P)

VCMPSS k, xmm, xmm, imm8 EVEX.LIG -mavx512f

_mm_cmpeq_ss __m128 _mm_cmpeq_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_cmple_ss __m128 _mm_cmple_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_cmplt_ss __m128 _mm_cmplt_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_cmpneq_ss __m128 _mm_cmpneq_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_cmpnle_ss __m128 _mm_cmpnle_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_cmpnlt_ss __m128 _mm_cmpnlt_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_cmpord_ss __m128 _mm_cmpord_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_cmpunord_ss __m128 _mm_cmpunord_ss(__m128 __a, __m128 __b)

VCMPSS xmm, xmm, xmm, imm8 VEX.LIG -mavxwith AVX enabled

_mm_comi_round_ss int _mm_comi_round_ss(__m128 A, __m128 B, const int P, const int R)

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

_mm_mask_cmp_round_ss_mask __mmask8 _mm_mask_cmp_round_ss_mask(__mmask8 M, __m128 X, __m128 Y, const int P, const int R)

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

_mm_mask_cmp_ss_mask __mmask8 _mm_mask_cmp_ss_mask(__mmask8 M, __m128 X, __m128 Y, const int P)

VCMPSS k {k}, 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.

More AVX instructions

All 253 AVX instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-189 (CMPSS)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. 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.