From: lkcl <lkcl@web>
Date: Tue, 11 Apr 2023 12:26:06 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: opf_rfc_ls012_v1~5
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=182e4ccb211d3e31028ce5b7c2414cd21a4e00c8;p=libreriscv.git

---

diff --git a/openpower/sv/rfc/ls012.mdwn b/openpower/sv/rfc/ls012.mdwn
index b4fdc7a9d..5a991c671 100644
--- a/openpower/sv/rfc/ls012.mdwn
+++ b/openpower/sv/rfc/ls012.mdwn
@@ -395,7 +395,10 @@ Deciding which instructions go into an ISA is extremely complex, costly,
 and a huge responsibility. In public standards mistakes are irrevocable,
 and in the case of an ISA the Opcode Allocation is a finite resource,
 meaning that mistakes punish future instructions as well.  This section
-therefore provides some Evaluation Guidance on the decision process.
+therefore provides some Evaluation Guidance on the decision process,
+particularly for people new to ISA development, given that this RFC
+is circulated widely and publicly.  Constructive feedback from experienced
+ISA Architects welcomed to improve this section.
 
 **Does anyone want it?**