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.
VADD.VV
RISC-V VADD.VV Instruction Details
Instruction ManualOP-VAdd active body elements at single width, retaining the low SEW result bits.
Instruction Syntax
vadd.vv vd, vs2, vs1[, v0.t]
Operand Breakdown
vd and vs2 are SEW-wide vector register groups; equal vector sources read identical initial elements, and same-EEW destination/source overlap is permitted.
vs1 is the second SEW-wide vector source, not an integer scalar register.
Omitting the mask means vm=1; v0.t means vm=0, with execution only where the body element's mask bit is 1.
Require V and the selected vtype. Body elements satisfy vstart ≤ i < vl; results wrap at SEW and tails follow vta. v0 cannot be read at both EEW=1 and SEW; masked vd cannot overwrite v0.
VVector OperationsInteger Arithmetic
Instruction Behavior
VADD.VV performs RVV single-width integer addition. Each active element computes vd[i] = vs2[i] + vs1[i], writes the low SEW bits, and wraps on integer overflow without trapping. With vm=0, v0 is the execution mask; 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.
VADD.VV Decode And Execute Animation
Starts from OP-V encoding fields, then shows how VADD single-width integer add reads active elements, wraps at SEW, and writes vd.
Instruction input
vadd.vv
Require valid vtype, enabled VS, and supported SEW; VL=0 updates nothing, including tails. Steps are teaching stages, not processor cycles.
Execution Context
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.
OP-V encodingvadd.vv
funct6
000000
vm
0
vs2
01000
vs1
01100
funct3
000
vd
00100
opcode
1010111
lane
0
1
2
3
4
5
6
7
v8
0x00fa
0x010b
0x011c
0x012d
0x013e
0x014f
0x0160
0x0171
+
+
+
+
+
+
+
+
v12
0x000d
0x0016
0x001f
0x0028
0x0031
0x003a
0x0043
0x004c
v0.t
1
0
1
1
1
0
1
1
v4
...
-
...
...
...
-
...
...
Current step
Show OP-V 32-bit encoding fields
vadd.vv uses OP-V encoding. The animation places fixed fields, register fields, vm, and the vs1 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.
Quick Understanding & Search Notes
VADD.VV performs ordinary integer addition element by element from two vector sources. Active elements read vs2[i] and vs1[i], write the low SEW result, and masked forms use v0.t to decide which body elements participate.
VADD uses OP-V vector-arithmetic encoding with funct6=000000; the .vv form is selected by funct3=000.
The vd, vs2 and vs1 data operands have EEW=SEW and register-group size follows LMUL; execution mask v0 has EEW=1.
Only body elements within the current vl are processed; vm=0 uses the v0 mask, vm=1 is unmasked, and masked-off destination elements follow the current mask policy.
Ordinary integer addition wraps at SEW width without saturation; VSADD/VSADDU provide saturating add.
Vector Execution Context
When reading VADD.VV, do not stop at the mnemonic. Official V-extension semantics also depend on the current vl, vtype, and mask state. .vv: two vector sources participate element by element.
Then check vtype
The current vtype supplies SEW, LMUL, tail policy, and mask policy; these affect element width, register-group size, and inactive/tail destination elements.
Then check vm/v0
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.
Common Usage Scenarios
Vectorized Loops
Assume V with e8,m1, vl=4, vstart=0, all vs2 elements=255, all vs1 elements=1, and v0 bits 1010 in lane order 0..3. The example vadd.vv v1, v2, v3, v0.t gives [0,policy,0,policy]; policy marks inactive elements governed by vma, without a definite value, and tails follow vta.
Array Ops
Assume V with e8,m1, vl=4, vstart=0, all vs2 elements=255, all vs1 elements=1, and v0 bits 1010 in lane order 0..3. The example vadd.vv v1, v2, v3, v0.t gives [0,policy,0,policy]; policy marks inactive elements governed by vma, without a definite value, and tails follow vta.
Pre-Use Checklist
Syntax Check
- vd and vs2 are SEW-wide vector register groups; equal vector sources read identical initial elements, and same-EEW destination/source overlap is permitted.
- vs1 is the second SEW-wide vector source, not an integer scalar register.
Semantic Check
- Omitting the mask means vm=1; v0.t means vm=0, with execution only where the body element's mask bit is 1.
- Require V and the selected vtype. Body elements satisfy vstart ≤ i < vl; results wrap at SEW and tails follow vta. v0 cannot be read at both EEW=1 and SEW; masked vd cannot overwrite v0.
Pitfalls / Common Confusions
VADD.VV is ordinary single-width integer add and keeps the low SEW bits; it is not saturating add.
With vm=0, only body elements whose v0 mask bit is 1 execute this add; masked-off destination elements follow the current mask policy.
Both vs2 and vs1 are vector sources interpreted with the current SEW/LMUL; no integer scalar register is read.
Masked vd cannot overlap v0; v0 cannot also be a SEW data source. Equal vector sources read identical initial elements.
FAQ
How do I choose VADD.VV, VADD.VX, and VADD.VI?
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.
Does VADD saturate or set an overflow flag?
No. VADD is ordinary two's-complement addition and keeps the low SEW bits. Saturating add is a separate RVV instruction category.