From e40fdf6b696cde3bf70fb24495b0195cffabf6c7 Mon Sep 17 00:00:00 2001 From: lkcl Date: Fri, 30 Aug 2019 11:10:58 +0100 Subject: [PATCH] --- simple_v_extension/specification/sv.setvl.mdwn | 3 --- 1 file changed, 3 deletions(-) diff --git a/simple_v_extension/specification/sv.setvl.mdwn b/simple_v_extension/specification/sv.setvl.mdwn index 516addf30..e65cefce1 100644 --- a/simple_v_extension/specification/sv.setvl.mdwn +++ b/simple_v_extension/specification/sv.setvl.mdwn @@ -3,11 +3,8 @@ sv.setvl allows optional setting of both MVL and of indirectly marking one of the scalar registers as being VL. Unlike the majority of other CSRs, which contain status bits that change behaviour, VL is closely interlinked with the instructions it affects and often requires arithmetic interaction. - Thus it makes more sense to actually *use* one of the scalar registers *as* VL. -A potential implementation optimisation technique involves keeping 5 bits which specify the scalar register in use as VL actually in the instruction decode phase. On detection of a CSRR rd, VL, if the cached copy of VL is not pointing to x0, the CSRR instruction is *replaced* with a "MV rd, vlcachedreg" instruction. See [[discussion]] for further details. - Format for Vector Configuration Instructions under OP-V major opcode: | 31|30 20|19 15|14 12|11 7|6 0| name | -- 2.30.2