When does rm matter for fcvt.wu.q?
When conversion requires rounding, rm or dynamic frm selects the rounding direction; out-of-range or NaN inputs follow the official invalid-conversion rule.
Convert quad-precision FP to unsigned 32-bit int. In OP-FP, fmt=Q (11) and rs2=WU (00001).
fcvt.wu.q converts a quad-precision source operand to an unsigned 32-bit integer result. Floating-point-to-integer conversion rounds according to rm and writes integer register rd.
Shows the Q-extension FCVT flow: decode OP-FP fields, fmt/rs2 conversion selection, the rm rounding field, read the floating-point source, then write the integer destination.
The word is split as an R-type OP-FP instruction; FCVT uses opcode 1010011.
The current example rounds to a 32-bit integer according to rm and shows NX because the source has a fractional part.
The current example rounds to a 32-bit integer according to rm and shows NX because the source has a fractional part.
This animation shows only Q-extension FCVT ISA-visible encoding, source/destination register direction, rounding field, and example fflags; it does not model FPU pipelines, exception handling, NaN payloads, or microarchitecture.
fcvt.wu.q converts a quad-precision source operand to an unsigned 32-bit integer result. Floating-point-to-integer conversion rounds according to rm and writes integer register rd.
Understand this scenario with real code like «fcvt.wu.q x10, f0, rtz # x10 = (unsigned)f0».
Understand this scenario with real code like «fcvt.wu.q x10, f0, rtz # x10 = (unsigned)f0».
When conversion requires rounding, rm or dynamic frm selects the rounding direction; out-of-range or NaN inputs follow the official invalid-conversion rule.
It differs by source/destination format, integer signedness, RV64 restrictions, and whether rounding or invalid conversion can occur.