You copied the Doc URL to your clipboard.

7.13 Comparison of condition code meanings in integer and floating-point code

The meaning of the condition code mnemonic suffixes depends on whether the condition flags were set by a floating-point instruction or by an A32 or T32 data processing instruction.

This is because:

  • Floating-point values are never unsigned, so the unsigned conditions are not required.
  • Not-a-Number (NaN) values have no ordering relationship with numbers or with each other, so additional conditions are required to account for unordered results.

The meaning of the condition code mnemonic suffixes is shown in the following table:

Table 7-3 Condition codes

SuffixMeaning after integer data processing instructionMeaning after floating-point instruction
NENot equalNot equal, or unordered
CSCarry setGreater than or equal, or unordered
HSUnsigned higher or sameGreater than or equal, or unordered
CCCarry clearLess than
LOUnsigned lowerLess than
MINegativeLess than
PLPositive or zeroGreater than or equal, or unordered
VSOverflowUnordered (at least one NaN operand)
VCNo overflowNot unordered
HIUnsigned higherGreater than, or unordered
LSUnsigned lower or sameLess than or equal
GESigned greater than or equalGreater than or equal
LTSigned less thanLess than, or unordered
GTSigned greater thanGreater than
LESigned less than or equalLess than or equal, or unordered
ALAlways (normally omitted)Always (normally omitted)


The type of the instruction that last updated the condition flags determines the meaning of the condition codes.
Was this page helpful? Yes No