Check vl first
The current vl determines the number of body elements. Typical code executes vsetvli, vsetivli, or vsetvl before this instruction.
Add each integer element to x[rs1]: vd[i] = vs2[i] + x[rs1].
VADD.VX performs RVV single-width integer addition. Each active element computes vd[i] = vs2[i] + x[rs1], using the same integer scalar source for every active element; the low SEW bits are written back and integer overflow wraps at SEW width. With vm=0, body elements whose mask bit is 0 do not execute this add, and their destination elements follow the current mask policy.
Starts from OP-V encoding fields, then shows how VADD single-width integer add reads active elements, wraps at SEW, and writes vd.
vadd.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 addition, mask control, and vd writeback. It does not model pipelines, caches, or timing.
VADD.VX adds the same integer scalar x[rs1] to each active element of vs2. It is used when vector data needs the same integer register value added to every active element, with the result still keeping the low SEW bits.
When reading VADD.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 «vadd.vx v1, v2, t0 # add scalar t0 to each active element».
Understand this scenario with real code like «vadd.vx v1, v2, t0 # add scalar t0 to each active element».
Use .vv when both operands are vector registers, .vx when one operand is an integer scalar register, and .vi for a small 5-bit signed constant.
No. VADD is ordinary two's-complement addition and keeps the low SEW bits. Saturating add is a separate RVV instruction category.