From: lkcl <lkcl@web>
Date: Sat, 9 Jul 2022 14:03:01 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: opf_rfc_ls005_v1~1225
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=dba1d3cb361ccbe0bf1a5c110bd7a2ac6d7f6733;p=libreriscv.git

---

diff --git a/openpower/sv/svp64_quirks.mdwn b/openpower/sv/svp64_quirks.mdwn
index 9ae60783d..935325989 100644
--- a/openpower/sv/svp64_quirks.mdwn
+++ b/openpower/sv/svp64_quirks.mdwn
@@ -208,10 +208,10 @@ Nemory Management
 instructions, these make no sense to Vectorise.
 
 However, it is really quite important to not be tempted to conclude that
-just because these instructions are un-vectoriseable, the opcode space
+just because these instructions are un-vectoriseable, the Prefix opcode space
 must be free for reiterpretation and use for other purposes. This would
 be a serious mistake because a future revision of the specification
-might *retire* the Scalar instruction, replace it with another.
+might *retire* the Scalar instruction, and, worse, replace it with another.
 Again this comes down to being quite strict about the rules: only Scalar
 instructions get Vectorised: there are *no* actual explicit Vector
 instructions.