Why is an unsigned REMUW remainder still sign-extended?
Unsignedness determines how the low 32-bit remainder is calculated; as a W instruction, REMUW then sign-extends that 32-bit result to 64 bits.
Unsigned remainder of 32-bit division, sign-extended to 64 bits
REMUW is an RV64-only unsigned remainder instruction. The lower 32 bits of rs1 divided by rs2 (both unsigned), remainder sign-extended to 64 bits. Division by zero: remainder = dividend (sign-extended). Unsigned division cannot overflow.
Starts with machine-code field decoding, then shows operand reads, instruction-specific execution, and ISA-visible state update.
This selector chooses only specification-defined division-result branches; it is not an exception, trap, or performance model.
The machine code is split by the current instruction format; the animation starts from encoding/decode.
This animation shows ISA-visible decode and state changes, not any specific CPU pipeline, cache, prediction, or timing implementation.
REMUW is RV64-only: it takes an unsigned remainder from the low 32 bits of both sources, then sign-extends that 32-bit value from bit 31 to 64 bits in rd.
Understand this scenario with real code like «remuw a0, a1, a2 # a0 = sign-extend(unsigned(a1[31:0]) % unsigned(a2[31:0]))».
Unsignedness determines how the low 32-bit remainder is calculated; as a W instruction, REMUW then sign-extends that 32-bit result to 64 bits.