From: Luke Kenneth Casson Leighton Date: Fri, 16 Sep 2022 00:57:24 +0000 (+0100) Subject: clarify table X-Git-Tag: opf_rfc_ls005_v1~416 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=bc1efc49ca384de0139fc89259669a3e7b410906;p=libreriscv.git clarify table --- diff --git a/openpower/sv/rfc/ls001.mdwn b/openpower/sv/rfc/ls001.mdwn index 25d4e9f6c..8c8e830cb 100644 --- a/openpower/sv/rfc/ls001.mdwn +++ b/openpower/sv/rfc/ls001.mdwn @@ -873,7 +873,7 @@ must be allocated to a Vectoriseable EXT000-063 "Defined Word" (Public v3.1 Section 1.6.3 definition) or not at all. -**another illegal example:** +**illegal unallocated scalar EXT0nn or EXT2nn:** | width | assembler | prefix? | suffix | description | |-------|-----------|--------------|-----------|---------------| @@ -889,8 +889,10 @@ and: | 64bit | ss.fishmv | 0x24!zero | 0x12345678| scalar SVP64Single:EXT2nn | | 64bit | sv.fishmv | 0x26nnnnnn | 0x12345678| vector SVP64:EXT2nn | -Both of these are illegal. The fact that there does not exist a -scalar "Defined Word" (even for EXT200-263) +Both of these Simple-V operations are illegally-allocated. The fact that +there does not exist a scalar "Defined Word" (even for EXT200-263) - the +unallocated block - means that the instruction may **not** be allocated in +the Simple-V space. \newpage{} # Use cases