From: lkcl <lkcl@web>
Date: Sun, 30 Jun 2019 08:51:51 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: convert-csv-opcode-to-binary~4326
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=e6fe88ea452287497af73dad096d34fc3237e5c3;p=libreriscv.git

---

diff --git a/simple_v_extension/sv_prefix_proposal/discussion.rst b/simple_v_extension/sv_prefix_proposal/discussion.rst
index 9731c6ec8..e73dfac2c 100644
--- a/simple_v_extension/sv_prefix_proposal/discussion.rst
+++ b/simple_v_extension/sv_prefix_proposal/discussion.rst
@@ -1,3 +1,17 @@
+RVC
+===
+
+The comment in the RVC section says that the Opcodes will be evaluated to see which are most useful to provide.
+
+This takes a huge amount of time and, if not *exactly* RVC, would require a special decode engine, taking up extra gates as well as need time to develop.
+
+Far better to just embed RVC into the opcode and prefix it. This is inline with the strategic principle behind SV: "No new opcodes, only prefixed augmentation"
+
+Taking an entire major 32 bit opcode (or two) seems logical (RV128 space). I type funct3 to specify the C type page, Imm 12 bits for the operation.
+
+Or, just "to hell with it" and just take the entire opcode and stuff C into it, no regard for R/I/U/S and instead do whatever we like.
+
+
 Questions
 =========