Is rd a floating-point register for FEQ.H?
No. rd is an integer register holding the Boolean result 0 or 1.
FEQ.H
RISC-V FEQ.H Instruction Details
Instruction ManualR-typehalf-precision floating-point equality compare; writes x[rd]=1 when true, otherwise 0.
Instruction Syntax
feq.h rd, rs1, rs2
Operand Breakdown
rd: destination integer register receiving a 0 or 1 comparison result.
rs1/rs2: source floating-point registers; compare instructions do not use an rm rounding mode.
ZfhFloating-Point Compare
Instruction Behavior
FEQ.H compares the half-precision floating-point values in f[rs1] and f[rs2] and writes the Boolean result to integer register rd. The encoding uses the OP-FP opcode, funct5=10100, fmt=H(10), and funct3=010; it is a quiet comparison that sets NV only for signaling NaN, and any NaN operand makes the result 0.
FEQ.H Decode And Execute Animation
Shows the Zfh-extension half-precision OP-FP flow: decode fields, read FP operands, perform FEQ semantics, then write rd.
rd
rs1
rs2
feq.h
,
,
Execution Context
FLEN=>=32 / fmt=H (10)
funct3: equality compare
fflags: example fflags remains 0
31..27
26..25
24..20
19..15
14..12
11..7
6..0
10100
FEQ
10
fmt=H
01100
rs2
01011
rs1
010
funct3=010
01010
rd
1010011
OP-FP
Execution Data Path
instruction
0xA4C5A553
opcode
1010011 -> OP-FP
funct5/fmt
10100 + H(10) -> FEQ.H
funct3
010 -> equality compare
rd/rs
a0(x10) / fa1(f11) / fa2(f12)
read
1.5, 1.5
FP op
1.5 == 1.5 -> 1
write
a0(x10) = 1; example fflags remains 0
Current Step
Fetch: show the 32-bit OP-FP encoding
The word is split as an R-type OP-FP instruction; half-precision OP-FP instructions use opcode 1010011.
encoding: 0xA4C5A553
syntax : feq.h a0(x10), fa1(f11), fa2(f12)
result : a0(x10) = 1; example fflags remains 0
The comparison result is written to integer register x[rd] and is only 0 or 1; compare instructions do not use rm.
Half-precision Calculation
rs1
fa1(f11) = 1.5
rs2
fa2(f12) = 1.5
result
1.5 == 1.5 -> 1
The comparison result is written to integer register x[rd] and is only 0 or 1; compare instructions do not use rm.
This animation shows only Zfh-extension ISA-visible OP-FP encoding, example numeric results, and fflags relationship; it does not model FPU pipelines, latency, every IEEE 754 corner case, or microarchitecture.
Quick Understanding & Search Notes
FEQ.H writes the half-precision FP comparison result to integer register x[rd]; the result is only 0 or 1.
OP-FP opcode is 1010011; funct5=10100, fmt=10, and funct3=010 select FEQ.H.
It writes 1 when rs1 == rs2 is true, otherwise 0; any NaN operand writes 0.
FEQ is a quiet comparison: qNaN leaves NV clear, while sNaN sets NV.
The comparison produces no FP result and has no rm rounding field; rd is an integer register.
Common Usage Scenarios
Comparison & Detection
Understand this scenario with real code like «feq.h x10, f0, f1 # x10 = (f0==f1)».
Floating-Point Conditions
Understand this scenario with real code like «feq.h x10, f0, f1 # x10 = (f0==f1)».
Pre-Use Checklist
Syntax Check
- rd: destination integer register receiving a 0 or 1 comparison result.
- rs1/rs2: source floating-point registers; compare instructions do not use an rm rounding mode.
Semantic Check
- Confirm the result is written to an integer register and is only 0 or 1.
- Confirm quiet/signaling comparison behavior for NaNs and NV matches the need.
Pitfalls / Common Confusions
Quiet comparisons set NV only for signaling NaNs; a quiet NaN only makes the result 0.
rd is an integer register and receives 0 or 1, not a floating-point value.
The comparison does not use the rm rounding mode.
FAQ
What happens on NaN operands for FEQ.H?
Any NaN operand makes the result 0; qNaN leaves NV clear, while sNaN sets NV.
Does FEQ.H use rm?
No. The funct3 field selects the comparison type, and the result is an integer Boolean.