How is FMV.H.X different from FCVT?
FMV copies the bit pattern; FCVT performs numeric conversion, can round, and can set exception flags.
Bit-copy low integer-register bits into a half-precision floating-point register.
Extension condition: RV32/RV64; requires Zfh 1.0 or Zfhmin 1.0 (both depend on F). In the standard privileged architecture, accessing FP state with FS=Off raises an illegal-instruction exception.
Provided by Zfh or Zfhmin (each depends on F), FMV.H.X bit-copies the low 16 bits of x[rs1] into f[rd] and NaN-boxes the half-precision result in the floating-point register. This is a bit move, not a numeric conversion.
Shows the Zfh/Zfhmin-extension FMV.H.X bit-pattern move: decode OP-FP fields, read the source bit pattern, then write the destination without numeric conversion.
Assumes required extensions and enabled FP state. Integer input covers XLEN bits; FP input supplies only the selected format's bit slice, ignoring upper NaN-box bits.
The word is split as an R-type OP-FP instruction; FMV bit moves use opcode 1010011.
FMV.H.X takes only the low 16 integer-source bits and NaN-boxes the half-precision result in the FP register.
This animation shows only Zfh/Zfhmin-extension FMV ISA-visible encoding and bit-pattern movement; it does not model FPU pipelines, numeric FP interpretation, exception handling, or microarchitecture.
FMV.H.X's core idea is bit-pattern movement. Use FCVT for numeric conversion and rounding; use FMV forms when preserving NaN payloads or inspecting raw encodings.
Understand this scenario with real code like «fmv.h.x f0, x10 # x10=0x1234C100; FLEN=64 -> f0=0xFFFFFFFFFFFFC100».
Understand this scenario with real code like «fmv.h.x f0, x10 # x10=0x1234C100; FLEN=64 -> f0=0xFFFFFFFFFFFFC100».
FMV copies the bit pattern; FCVT performs numeric conversion, can round, and can set exception flags.
No. It is neither arithmetic nor numeric conversion.