From: pham.michael.98@a029fe8ac2da19fcd7269c492cf0410b2e5fd4cc <phammichael98@web>
Date: Sun, 15 Sep 2019 01:20:38 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: convert-csv-opcode-to-binary~4056
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=8f2d8b516078d2e38d739630d64691502c61199f;p=libreriscv.git

---

diff --git a/resources.mdwn b/resources.mdwn
index 2ad599f42..2da068365 100644
--- a/resources.mdwn
+++ b/resources.mdwn
@@ -12,8 +12,7 @@ To fully take advantage of the RISC-V ecosystem, it is important to be compliant
 * Working draft of the proposed RISC-V Bitmanipulation extension: <https://github.com/riscv/riscv-bitmanip/blob/master/bitmanip-draft.pdf>
 * RISC-V "V" Vector Extension: <https://riscv.github.io/documents/riscv-v-spec/>
 
-Note: As far as I know, we aren't using the RISC-V V Extension directly at the moment. But, I am putting it here for informative comparison purposes to our own vector extension called SV.
-
+Note: As far as I know, we aren't using the RISC-V V Extension directly at the moment. However, there are many wiki pages that make a reference to the V extension so it would be good to include it here as a reference for comparative/informative purposes with regard to Simple-V.
 # IEEE Standard for Floating-Point Arithmetic (IEEE 754)
 
 Almost all modern computers follow the IEEE Floating-Point Standard. Of course, we will follow it as well for interoperability.