Does VREM.VX 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.
vector-scalar signed integer remainder; writes each remainder to vd, and divide by zero does not trap.
VREM.VX is a RISC-V V extension vector-scalar signed integer remainder instruction. Each active element uses vs2 as the dividend and the x[rs1] scalar value 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 and vstart=0. Fix VLEN=4096 and VLMAX=4096/16=256; equal-width sources/destination may overlap. The signed quotient rounds toward zero; a nonzero remainder has the dividend’s sign. MIN/-1 has remainder zero. A zero divisor returns the dividend. XLEN>SEW takes low scalar bits; XLEN<SEW sign-extends even for unsigned arithmetic; x0 supplies zero. Masked vd cannot be v0; v0 cannot supply both mask and SEW data. Enter nonnegative element bit patterns. VL=0 leaves vd unchanged. Only body is shown; no definite inactive/tail values. Teaching stages are not processor cycles.
vrem.vx uses OP-V encoding. The animation places fixed fields, register fields, vm, and the rs1 field in one encoding strip.
This animation shows OP-V field decode, active-element reads, signed remainder, mask control, and vd writeback. These are teaching stages; they do not model pipelines, caches, or timing.
VREM.VX does not raise a divide-by-zero exception. For active elements within the current vl, it reads vs2 as the dividend and the x[rs1] scalar value as the divisor, writes the signed remainder, and with vm=0 only body elements whose v0.t bit is 1 execute.
Syntax: vrem.vx vd, vs2, rs1[, v0.t]; omit the mask for vm=1, include v0.t for vm=0. 32-bit OP-V: opcode=1010111, funct3=110 (OPMVX), funct6=100011.
vs2[i] is the dividend; x[rs1] supplies the scalar divisor: XLEN>SEW takes low SEW bits; XLEN<SEW sign-extends even for unsigned arithmetic; x0 supplies zero. Compute signed SEW remainders. A zero divisor returns the dividend; a nonzero remainder has the dividend's sign, and minimum divided by -1 has 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 and vstart=0; VLEN=4096. Steps are not processor cycles.
Assume enabled V/VS, valid m1, supported SEW, VLEN≥128 and XLEN=64, vl=4, vstart=0, v0.mask[0..3]=1111 and initialized sources. SEW=8, a1=3, v12=[249(-7),7,128(-128),5] → v8=[255(-1),1,254(-2),2]. Inactive/tail follow vma/vta; vl=0 leaves vd unchanged.
Assume enabled V/VS, valid m1, supported SEW, VLEN≥128 and XLEN=64, vl=4, vstart=0, v0.mask[0..3]=1111 and initialized sources. SEW=8, a1=3, v12=[249(-7),7,128(-128),5] → v8=[255(-1),1,254(-2),2]. Inactive/tail follow vma/vta; vl=0 leaves vd 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.VX 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.