Do these floating-point instructions use vxrm?
No. Ordinary RVV floating-point operations and FP conversions use floating-point frm or an instruction-specified fixed rounding mode; vxrm is for fixed-point rounding instructions.
Add 2*SEW float elements of vs2 with widened vs1 (SEW) elements, writing 2*SEW result to vd.
VFWADD.WV computes vd[i] = vs2[i] + widen(vs1[i]) for active elements. vs2 is already 2×SEW wide, vs1 is SEW wide, and the result is 2×SEW wide. The narrow FP source widens exactly before double-width addition under dynamic frm. The animation shows finite binary64 plus binary32 values under RNE.
Decode the OP-V encoding and execute lane-wise widening FP addition: vs2 is already 2*SEW=64 wide, while vs1[i] is exactly widened from SEW=32 before writing the 2*SEW=64 result.
lane 0: 1 + 0.5 -> 1.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.
VFWADD.WV keeps the add result at wider precision, unlike single-width VFADD.
Syntax: vfwadd.wv vd, vs2, vs1[, v0.t]. 32-bit OP-V: opcode=1010111, funct3=001, funct6=110100. vs1 selects the narrow vector source.
vs2 and vd have EEW=2×SEW, EMUL=2×LMUL; vs1 has EEW=SEW, EMUL=LMUL. Groups with EMUL=2/4/8 align to their size; EMUL>8 is reserved, while EMUL≤1 does not require even register numbers.
Narrow vs1 widens exactly before addition to wide vs2 under dynamic frm. Wide vs2 may overlap the equal-width destination, but cannot share a register with narrow vs1. Every vector FP instruction still requires valid frm, including at vl=0; invalid frm use is reserved. vxrm is not used.
Narrow-source/wide-destination overlap requires source EMUL≥1 and equal highest register numbers; legal different-EEW overlap forces mask/tail agnostic. A masked destination cannot include v0; one register cannot be read as different-EEW data and mask sources.
Optional v0.t means vm=0; omission means vm=1. Active elements satisfy vstart≤i<vl with the mask enabled; only active-element exceptions accrue in fflags. Prestart elements do not update or raise exceptions. At vl=0 or vstart≥vl no destination elements, including tails, update. Other inactive/tail elements follow vma/vta; ta/ma does not guarantee zeros. Successful execution resets vstart=0.
Require the extensions, supported FP formats, valid vtype, and enabled VS/FS; with H and virtualization V=1, vsstatus.VS/FS must also be enabled. This animation fixes SEW=32, LMUL=m1, VLEN=4096, vstart=0, ta/ma, and finite inputs; it does not fully simulate NaNs, infinities, fflags, or microarchitectural cycles.
Assume enabled extensions and VS/FS, valid vtype, supported formats, frm=RNE, e32,m1, VLMAX≥4, and a0=4; vsetvli sets vl=4 and vstart=0. Omit v0.t for unmasked execution: v4/v5(binary64)=[1,2,-3,0], v8(binary32)=[0.5,0.5,0.5,0.5] → v2/v3=[1.5,2.5,-2.5,0.5]. Tails follow ta without guaranteed zeros.
Assume enabled extensions and VS/FS, valid vtype, supported formats, frm=RNE, e32,m1, VLMAX≥4, and a0=4; vsetvli sets vl=4 and vstart=0. Omit v0.t for unmasked execution: v4/v5(binary64)=[1,2,-3,0], v8(binary32)=[0.5,0.5,0.5,0.5] → v2/v3=[1.5,2.5,-2.5,0.5]. Tails follow ta without guaranteed zeros.
No. Ordinary RVV floating-point operations and FP conversions use floating-point frm or an instruction-specified fixed rounding mode; vxrm is for fixed-point rounding instructions.