Does VREM.VV trap on divide by zero?
No. The official V extension defines the divide-by-zero result: the remainder is the dividend, and the instruction itself does not raise a divide-by-zero trap.
VREM.VV computes signed SEW remainders for active elements; a nonzero remainder has the dividend’s sign, and a zero divisor returns the dividend.
VREM.VV is a RISC-V V extension vector-vector signed integer remainder instruction. Each active element uses vs2 as the dividend and the same-lane vs1 element as the divisor, computes the SEW-width remainder, and writes vd; zero divisors and signed overflow cases use the official specified results without a divide-by-zero trap.
Starts from OP-V encoding fields, then shows how VREM computes each signed remainder and applies the official divide-by-zero and signed-overflow special cases.
Require V 1.0, enabled vector state and valid supported vtype/SEW. Fix LMUL=m1, vstart=0, VLEN=4096 and VLMAX=4096/16=256. An ordinary masked vd cannot be v0; equal-width source/destination overlap is legal. Both sources are interpreted as signed SEW integers; a nonzero remainder has the dividend’s sign. Enter nonnegative SEW bit patterns. When v0 supplies the EEW=1 mask it cannot also supply SEW data. VL=0 updates no destination elements. Only body is shown without definite inactive/tail values. Steps are teaching stages, not processor cycles.
vrem.vv uses OP-V encoding. The animation places fixed fields, register fields, vm, and the vs1 field in one encoding strip.
This animation shows OP-V field decode, active-element reads, SEW-width signed integer remainder, mask control, and vd writeback. These are teaching stages; they do not model pipelines, caches, or timing.
VREM.VV does not raise a divide-by-zero exception. For active elements within the current vl, it reads vs2 as the dividend and the same-lane vs1 element as the divisor, writes the signed remainder, and with vm=0 only body elements whose v0.t bit is 1 execute.
Syntax: vrem.vv vd, vs2, vs1[, v0.t]; omit the mask for vm=1, include v0.t for vm=0. 32-bit OP-V: opcode=1010111, funct3=010 (OPMVV), funct6=100011.
vs2[i] is the dividend and vs1[i] is the divisor, interpreted as signed SEW integers. A nonzero remainder has the dividend's sign. A zero divisor returns the dividend; minimum divided by -1 returns remainder zero.
Active body satisfies vstart≤i<vl with the mask enabled. Inactive/tail follow vma/vta: retain or agnostic, without a fixed value to rely on. vl=0 updates no destination elements.
Same-width sources/destination may overlap. Masked vd cannot be v0; v0 cannot provide both the EEW=1 mask and SEW data. Group starts align to EMUL, EMUL≤8.
Require V 1.0, enabled vector state and valid supported vtype/SEW. The animation fixes m1, vstart=0 and VLEN=4096; teaching steps are not processor cycles.
Assume enabled V/VS, valid m1, supported SEW, VLEN≥128, vl=4, vstart=0, v0.mask[0..3]=1111 and initialized sources. SEW=8, v12=[249(-7),7,128(-128),5], v4=[3,253(-3),255(-1),0] → v8=[255(-1),1,0,5]. Compute element-wise remainders; inactive/tail follow vma/vta. vl=0 leaves the destination unchanged.
Assume enabled V/VS, valid m1, supported SEW, VLEN≥128, vl=4, vstart=0, v0.mask[0..3]=1111 and initialized sources. SEW=8, v12=[249(-7),7,128(-128),5], v4=[3,253(-3),255(-1),0] → v8=[255(-1),1,0,5]. Compute element-wise remainders; inactive/tail follow vma/vta. vl=0 leaves the destination unchanged.
No. The official V extension defines the divide-by-zero result: the remainder is the dividend, and the instruction itself does not raise a divide-by-zero trap.
VREM.VV writes the remainder; the paired VDIV form writes the quotient for the same divide relation. Both use the same divide-by-zero and signed-overflow special-case rules.