From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Sat, 24 Nov 2018 04:02:21 +0000 (+0000)
Subject: clarify elwidth section
X-Git-Tag: convert-csv-opcode-to-binary~4830
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=61e37b1de41074e3a658b465133ce15e0d65459b;p=libreriscv.git

clarify elwidth section
---

diff --git a/simple_v_extension/specification.mdwn b/simple_v_extension/specification.mdwn
index 542919af7..930ab64fe 100644
--- a/simple_v_extension/specification.mdwn
+++ b/simple_v_extension/specification.mdwn
@@ -1637,7 +1637,9 @@ to the result element's bitwidth.
 
 If truncation occurs, i.e. the top MSBs of the result are lost,
 this is "Officially Not Our Problem", i.e. it is assumed that the
-programmer actually desires the result to be truncated.
+programmer actually desires the result to be truncated.  i.e. if the
+programmer wanted all of the bits, they would have set the destination
+elwidth to accommodate them.
 
 ## Polymorphic elwidth on LOAD/STORE <a name="elwidth_loadstore"></a>