Is rd a floating-point register for FEQ.D?
No. rd is an integer register holding the Boolean result 0 or 1.
Double-precision floating-point equality compare; writes the 0/1 Boolean result to integer register rd.
32-bit OP-FP: opcode=1010011, funct5=10100, fmt=01; funct3=010, no rm.
rd is integer x0–x31; rs1/rs2 are FP f0–f31 or ABI names. x0 discards the result while retaining NV side effects.
RV32/RV64 D (requires F); enable required extensions and FP state. Sources narrower than FLEN require valid NaN-boxing, otherwise use canonical qNaN.
Write 1 for equality, otherwise 0; any NaN writes 0. Only sNaN sets NV; qNaN does not clear old NV. fflags accrues exceptions.
One source register must have one initial value. The animation starts with fflags=0; teaching steps are not hardware cycles.
FEQ.D belongs to the D extension, which depends on F. It compares the double-precision floating-point values in f[rs1] and f[rs2], then writes the Boolean result to integer register rd. FEQ is a quiet comparison: a quiet NaN makes the result 0 without setting NV, while a signaling NaN sets NV. The comparison result is not a floating-point value and the instruction has no rm operand.
Shows the D-extension double-precision OP-FP flow: decode fields, read FP operands, perform FEQ semantics, then write rd.
The word is split as an R-type OP-FP instruction; double-precision OP-FP instructions use opcode 1010011.
The comparison result is written to integer register x[rd] and is only 0 or 1; compare instructions do not use rm.
The comparison result is written to integer register x[rd] and is only 0 or 1; compare instructions do not use rm.
Assumes required extensions and FS enabled, valid NaN-boxing, and initial fflags=0. Finite inputs use the exact whitelist; signed zeros, infinities, qNaN, and sNaN are supported. Other inputs stop execution. One source register must have one initial value; rd=x0 discards only the integer write while NV still accrues. Steps are teaching views.
This animation shows only D-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.
In the D extension, which depends on F, FEQ.D bridges FP comparison to an integer Boolean result: it reads two FP registers but writes x[rd]=0/1.
Understand this scenario with real code like «feq.d x10, f0, f1 # f0=1.5, f1=1.5 -> x10=1; no new flags».
Understand this scenario with real code like «feq.d x10, f0, f1 # f0=1.5, f1=1.5 -> x10=1; no new flags».
No. rd is an integer register holding the Boolean result 0 or 1.
Any NaN produces result 0; FEQ sets NV only for signaling NaN.
No. FP comparisons do not round; the encoded funct3 selects the compare kind.