Check vl first
Body elements satisfy vstart ≤ i < vl; vstart≥vl leaves the destination unchanged. Set supported vl/vtype and initialize the sources and v0 first.
Add active body elements at single width, retaining the low SEW result bits.
VADD.VI performs RVV single-width integer addition on active elements: vd[i] = vs2[i] + sign_extend(imm). imm is a 5-bit signed immediate (-16..15), sign-extended to SEW; 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. Requires V 1.0 and support for the selected vtype on RV32/RV64. Body elements satisfy vstart ≤ i < vl; vstart≥vl leaves the destination unchanged. Tails follow vta.
Starts from OP-V encoding fields, then shows how VADD single-width integer add reads active elements, wraps at SEW, and writes vd.
Require valid vtype, enabled VS, and supported SEW; VL=0 updates nothing, including tails. Steps are teaching stages, not processor cycles.
The teaching model fixes LMUL=m1 and vstart=0 and shows only body elements in the selected VL. It fixes VLEN=4096, VLMAX=4096/16=256, and assumes support for the selected SEW; equal vector sources require equal elements. In ordinary masked forms, inactive and tail elements follow vtype.vma/vta and the result row does not invent a definite value; VADC/VMADC/VSBC/VMSBC execute every body element, with v0 bits used only as carry/borrow-in.
vadd.vi uses OP-V encoding. The animation places fixed fields, register fields, vm, and the imm 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.VI adds a 5-bit signed immediate to each active element of vs2. The immediate is sign-extended to SEW, so this form is for small constants in the -16..15 range.
When reading VADD.VI, do not stop at the mnemonic. Official V-extension semantics also depend on the current vl, vtype, and mask state. .vi: one vector source and a small immediate participate.
Body elements satisfy vstart ≤ i < vl; vstart≥vl leaves the destination unchanged. Set supported vl/vtype and initialize the sources and v0 first.
The current vtype supplies SEW, LMUL, tail policy, and mask policy; these affect element width, register-group size, and inactive/tail destination elements.
With vm=0, v0.t selects active body elements; omitting the mask operand means vm=1, unmasked. Inactive and tail elements follow current vma/vta.
Assume V with e8,m1, vl=4, vstart=0, all vs2 elements=255, imm=-1, and v0 bits 1010 in lane order 0..3. The example vadd.vi v1, v2, -1, v0.t gives [254,policy,254,policy]; policy marks inactive elements governed by vma, without a definite value, and tails follow vta.
Assume V with e8,m1, vl=4, vstart=0, all vs2 elements=255, imm=-1, and v0 bits 1010 in lane order 0..3. The example vadd.vi v1, v2, -1, v0.t gives [254,policy,254,policy]; policy marks inactive elements governed by vma, without a definite value, and tails follow vta.
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.