Is VSLIDEUP.VX a memory move?
No. It moves data among vector-register elements and does not access memory.
VSLIDEUP.VX
RISC-V VSLIDEUP.VX Instruction Details
Instruction ManualR-typeSlide vector elements toward higher indexes.
Instruction Syntax
vslideup.vx vd, vs2, rs1, vm
Operand Breakdown
Destination rd: register receiving the operation result.
Source rs1: register holding the first operand.
Source rs2: register holding the second operand.
VVector PermutationSlide
Related Search Terms
Instruction Behavior
VSLIDEUP.VX moves vs2 elements by offset x[rs1] toward higher indexes into vd. Destination elements below the offset are unchanged; other active elements are taken from lower-numbered source elements.
Quick Understanding & Search Notes
VSLIDEUP.VX moves element positions within a vector register, useful for windows, shift-register patterns, and boundary insertion.
Slideup-class instructions have destination/source overlap restrictions to avoid writes destroying later reads.
VSLIDEUP moves source elements into higher-numbered destination positions; destination elements below the offset are unchanged.
vm=0 uses v0 as the execution mask; inactive and tail elements follow current policies.
Common Usage Scenarios
Data Shift
Understand this scenario with real code like «vslideup.vx v8, v12, x5, v0.t».
Convolution
Understand this scenario with real code like «vslideup.vx v8, v12, x5, v0.t».
Shift Register
Understand this scenario with real code like «vslideup.vx v8, v12, x5, v0.t».
Pre-Use Checklist
Syntax Check
- Confirm the current instruction format is R-type.
- Confirm the operand order matches the example.
Semantic Check
- Ensure the destination register usage is compatible with the calling convention.
- Confirm this is not the lower-level form of a pseudo-instruction expansion.
Pitfalls / Common Confusions
The destination vector register group cannot overlap the source group.
OFFSET comes from x[rs1]; when XLEN>SEW it is not truncated to SEW.
Destination elements 0..OFFSET-1 remain unchanged.