From 457e908cff598d66a804d506b968887bffc03ee8 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Fri, 5 Oct 2018 04:47:13 +0100 Subject: [PATCH] simplify LOAD/STORE section --- simple_v_extension/specification.mdwn | 64 ++++++--------------------- 1 file changed, 14 insertions(+), 50 deletions(-) diff --git a/simple_v_extension/specification.mdwn b/simple_v_extension/specification.mdwn index e0ce2a543..ac9823e3c 100644 --- a/simple_v_extension/specification.mdwn +++ b/simple_v_extension/specification.mdwn @@ -667,58 +667,22 @@ Similar rules apply to the destination register. ## LOAD / STORE Instructions and LOAD-FP/STORE-FP -The original RISC-V scalar LOAD/STORE and LOAD-FP/STORE-FP functionality -do not change in SV, however with both the source and destination -registers being able to indepdendently be marked as scalar, vector -and also "Packed SIMD", *and*, just as with C.MV, predication to be optionally -applied to both source **and destination**, it is specifically worthwhile -writing out the pseudo-code to ensure that implementations are correct. +An earlier draft of SV modified the behaviour of LOAD/STORE. This +actually undermined the fundamental principle of SV, namely that there +be no modifications to the scalar behaviour (except where absolutely +necessary), in order to simplify an implementor's task if considering +converting a pre-existing scalar design to support parallelism. + +So the original RISC-V scalar LOAD/STORE and LOAD-FP/STORE-FP functionality +do not change in SV, however just as with C.MV it is important to note +that dual-predication is possible. Using the template outlined in +the section "Vectorised dual-op instructions", the pseudo-code covering +scalar-scalar, scalar-vector, vector-scalar and vector-vector applies, +where SCALAR_OPERATION is as follows, exactly as for a standard +scalar RV LOAD operation: -For the case where both source and destination use the same predication -register, the following seudo-code applies (excludes "Packed SIMD" for -simplicity): - -  ps = get_pred_val(FALSE, rd); - - get_int_reg(reg, i): - if (intcsr[reg]->isvec) - return intregs[reg+i] - else - return intregs[reg] - - for (int i=0; iisvec) { # destination is marked as scalar - break; # stop at first element (remember: predication) - } - } - -Taking CSR (SIMD) bitwidth into account involves using the vector -length and register encoding according to the "Bitwidth Virtual Register -Reordering" scheme shown in the Appendix (see function "regoffs"). - -STORE is similarly augmented. - -For the case where the src and destination register use different -predication targets, the pseudocode is similarly modified. It is -identical to the pseudocode for C.MV (above): - - function op_load(rd, rs) # LOAD not VLOAD! -  rd = int_csr[rd].active ? int_csr[rd].regidx : rd; -  rs = int_csr[rs].active ? int_csr[rs].regidx : rs; -  ps = get_pred_val(FALSE, rs); # predication on src -  pd = get_pred_val(FALSE, rd); # ... AND on dest -  for (int i = 0, int j = 0; i < VL && j < VL;): - if (int_csr[rs].isvec) while (!(ps & 1<