Does VFRSUB.VF use vxrm?
No. Ordinary RVV FP arithmetic uses the floating-point rounding environment frm or the instruction-defined FP rounding rule; vxrm is for fixed-point rounding instructions.
VFRSUB.VF performs vector-scalar FP reverse subtract on active elements within VL: vd[i] = f[rs1] - vs2[i].
Active elements compute vd[i] = f[rs1] - vs2[i]: scalar minus vector, rounded using dynamic frm, with exceptions accrued in fflags. vm=0 uses v0.t; vm=1 is unmasked. vxrm does not control this operation.
Decode the OP-V encoding and execute reverse FP subtraction lane by lane: each active lane computes f[rs1] - vs2[i].
lane 0: 1.5 - 1 -> 0.5
This lane follows the current-step highlight; the remaining lane results appear below.
V-extension FP instructions use the OP-V major opcode, with funct6, source registers, vm, funct3, vd, and opcode fields.
VFRSUB.VF is best understood through OP-V encoding, the floating-point scalar register f[rs1], v0.t masking, and per-element vd[i] = f[rs1] - vs2[i].
32-bit OP-V encoding: funct6=100111, funct3=101, opcode=1010111. rs1 selects an FP f register, not an integer register. At FLEN>SEW a valid NaN box supplies low SEW bits; otherwise use canonical NaN. FLEN<SEW is reserved.
Vector operands and results have SEW bits and EMUL=LMUL. Same-width source/destination overlap is legal; equal sources require consistent initial bits. An ordinary masked destination cannot overlap v0.
Optional assembly vm is written v0.t for vm=0; omission means vm=1. Active elements satisfy vstart≤i<vl with the mask enabled. One source register cannot be read as both an EEW=1 mask and SEW-wide data.
Prestart elements are unchanged. At vstart≥vl or vl=0 all destination elements, including tails, are unchanged. Other inactive/tail elements follow vma/vta; ta/ma does not guarantee zeroing.
Each element computes f[rs1] - vs2[i], rounded using dynamic frm; active-element exceptions accrue in fflags.
V 1.0 applies to RV32/RV64, includes FP32/FP64, and depends on F/D; SEW=16 arithmetic requires Zvfh. Require valid vtype, supported widths, and enabled VS/FS; with H and virtualization V=1, vsstatus.VS/FS must also be enabled. All these vector FP instructions require valid frm, even if independent of it or at vl=0. vxrm does not control them.
Animation steps are educational, not processor cycles. Fixed VLEN=4096, LMUL=m1, vstart=0, valid vtype, and enabled VS/FS apply; input formats, fixed rounding, and model limits are stated in the animation. VF scalars use FLEN=64, assuming valid NaN-boxing at SEW=32.
Assume V/VS/FS enabled, valid vtype, valid frm=RNE, supported e32,m1, VLMAX≥4, and a0=4; vsetvli sets vl=4 and vstart=0. Inputs are binary32; ft0, when used, is validly NaN-boxed at FLEN=64. Omitting v0.t makes this unmasked: ft0=8, v2=[1,2,3,4] → v1=[7,6,5,4]. Tails follow ta without assumed zeroing.
No. Ordinary RVV FP arithmetic uses the floating-point rounding environment frm or the instruction-defined FP rounding rule; vxrm is for fixed-point rounding instructions.
vm=0 uses v0.t as the execution mask; vm=1 is unmasked. It is not an ordinary data source register.