From: Luke Kenneth Casson Leighton Date: Tue, 6 Sep 2022 13:51:55 +0000 (+0100) Subject: more clarification on ranges X-Git-Tag: opf_rfc_ls005_v1~648 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=52fe8c5f9db116630e69164b40a99664bef8f93d;p=libreriscv.git more clarification on ranges --- diff --git a/openpower/sv/svp64.mdwn b/openpower/sv/svp64.mdwn index dae7e7b29..d05e2f5ba 100644 --- a/openpower/sv/svp64.mdwn +++ b/openpower/sv/svp64.mdwn @@ -592,14 +592,19 @@ If EXTRA2 is zero will map to | 10 | Vector | `r0-r124`/4 | `RA 0b00` | | 11 | Vector | `r2-r126`/4 | `RA 0b10` | -Note that unlike in EXTRA3, in EXTRA2 the GPR Vectors may only start from -`r0, r2, r4, r6, r8` and likewise FPR Vectors as there is insufficient -bits to cover the full range. +**Note that unlike in EXTRA3, in EXTRA2**: + +* the GPR Vectors may only start from + `r0, r2, r4, r6, r8` and likewise FPR Vectors. +* the GPR Scalars may only go from `r0, r1, r2.. r63` and likewise FPR Scalars. + +as there is insufficient bits to cover the full range. ## CR Field EXTRA3 CR Field encoding is essentially the same but made more complex due to CRs being bit-based. See [[svp64/appendix]] for explanation and pseudocode. -Note that Vectors may only start from `CR0, CR4, CR8, CR12, CR16`... +Note that Vectors may only start from `CR0, CR4, CR8, CR12, CR16, CR20`... +and Scalars may only go from `CR0, CR1, ... CR31` Encoding shown MSB down to LSB