Check vl first
The current vl determines the number of body elements. Typical code executes vsetvli, vsetivli, or vsetvl before this instruction.
Subtract vector elements from a scalar register.
VRSUB.VX computes x[rs1] - vs2[i] for active elements and writes the low SEW bits to vd.
Starts from OP-V encoding fields, then shows how VRSUB subtracts vs2 from the second source, wraps at SEW, and writes vd.
vrsub.vx uses OP-V encoding. The animation places fixed fields, register fields, vm, and the rs1 field in one encoding strip.
This animation shows only ISA-visible relationships from the official V extension: OP-V field decode, active-element reads, SEW-width integer reverse subtraction, mask control, and vd writeback. It does not model pipelines, caches, or timing.
VRSUB.VX is reverse subtraction: each active element computes x[rs1] - vs2[i]. It is not a synonym for VSUB.VX; the operand order is reversed.
When reading VRSUB.VX, do not stop at the mnemonic. Official V-extension semantics also depend on the current vl, vtype, and mask state. .vx: one vector source and one integer scalar source participate.
The current vl determines the number of body elements. Typical code executes vsetvli, vsetivli, or vsetvl before this instruction.
The current vtype supplies SEW, LMUL, tail policy, and mask policy; these affect element width, register-group size, and inactive/tail destination elements.
For ordinary vector instructions with vm, vm=0 uses v0 as the execution mask and vm=1 is unmasked. A few forms such as VMERGE use v0 as data-selection input.
Understand this scenario with real code like «vrsub.vx v8, v12, x5, v0.t».
Understand this scenario with real code like «vrsub.vx v8, v12, x5, v0.t».
VRSUB.VX computes x[rs1] - vs2[i], while VSUB.VX computes vs2[i] - x[rs1]. Subtraction is not commutative, so the results usually differ.
The result keeps the low SEW bits and wraps at SEW width, with no integer trap or borrow flag.