Check vl first
The current vl determines the number of body elements. Typical code executes vsetvli, vsetivli, or vsetvl before this instruction.
Slide vector elements toward lower indexes.
VSLIDEDOWN.VI moves vs2 elements by offset uimm toward lower indexes into vd. A source index outside VLMAX writes zero to the destination element.
Starts from OP-V encoding fields, then shows how VSLIDEDOWN reads higher-numbered source elements by OFFSET; destination elements whose source index is >= VLMAX receive zero.
vslidedown.vi uses OP-V encoding. The animation places fixed fields, register fields, vm, and the uimm field in one encoding strip.
This animation shows only ISA-visible relationships from the official V extension: OP-V field decode, active-element reads, element-index/packing/select/move rearrangement integer slide down, boundary/selection rules, and vd writeback. It does not model pipelines, caches, or timing.
vslidedown.vi uses uimm as OFFSET: active element i reads vs2[i+OFFSET]; if i+OFFSET >= VLMAX, the result is zero.
When reading VSLIDEDOWN.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.
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 «vslidedown.vi v8, v12, 3, v0.t».
Understand this scenario with real code like «vslidedown.vi v8, v12, 3, v0.t».
Understand this scenario with real code like «vslidedown.vi v8, v12, 3, v0.t».
When the source index i+OFFSET for an active element is greater than or equal to VLMAX, that destination element writes zero by the official rule.
No. It only rearranges vector-register elements or inserts a scalar-register value; memory loads and stores are handled by vector load/store instructions.