Check vl first
The current vl determines the number of body elements. Typical code executes vsetvli, vsetivli, or vsetvl before this instruction.
Element-wise vector integer subtraction.
VSUB.VX computes vs2[i] - x[rs1] for active elements and writes the low SEW bits to vd.
Starts from OP-V encoding fields, then shows how VSUB subtracts the second source from vs2, wraps at SEW, and writes vd.
vsub.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 subtraction, mask control, and vd writeback. It does not model pipelines, caches, or timing.
VSUB.VX computes vs2[i] - x[rs1] for each active element. The scalar is on the right side; use VRSUB.VX for x[rs1] - vs2[i].
When reading VSUB.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 «vsub.vx v1, v2, t0 # v1[i] = v2[i] - t0».
Understand this scenario with real code like «vsub.vx v1, v2, t0 # v1[i] = v2[i] - t0».
Understand this scenario with real code like «vsub.vx v1, v2, t0 # v1[i] = v2[i] - t0».
No. VSUB.VX is vs2[i] - x[rs1]. Use VRSUB.VX for scalar minus vector.
The VX scalar comes from integer register rs1 and is used for each active element.