How is FMV.X.H different from FCVT?
FMV copies the bit pattern; FCVT performs numeric conversion, can round, and can set exception flags.
Bit-copy a half-precision floating-point encoding to an integer register.
Provided by Zfh or Zfhmin (each depends on F), FMV.X.H bit-copies the half-precision floating-point encoding in f[rs1] into x[rd], filling the upper XLEN-16 integer-register bits with copies of bit 15. This is a bit move, not a floating-point-to-integer numeric conversion; it does not round and sets no floating-point exception flags.
Shows the Zfh/Zfhmin-extension FMV.X.H bit-pattern move: decode OP-FP fields, read the source bit pattern, then write the destination without numeric conversion.
The word is split as an R-type OP-FP instruction; FMV bit moves use opcode 1010011.
FMV.X.H sign-extends half-precision bit 15 into the upper XLEN=32 bits; it does not perform numeric conversion.
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.X.H'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.x.h x10, f0 # x10 = sign_extend(f0[15:0]) to XLEN bits».
Understand this scenario with real code like «fmv.x.h x10, f0 # x10 = sign_extend(f0[15:0]) to XLEN bits».
FMV copies the bit pattern; FCVT performs numeric conversion, can round, and can set exception flags.
No. It is neither arithmetic nor numeric conversion.