clarify

diff --git a/simple_v_extension.mdwn b/simple_v_extension.mdwn
index 554d67f03f040a643bf7c1562a10ffcaf1e450f5..2f2402c8863785acb1ac3e27eb7800483f745fef 100644 (file)
--- a/simple_v_extension.mdwn
+++ b/simple_v_extension.mdwn
@@ -478,7 +478,7 @@ register files:
 
 An array of 32 4-bit CSRs is needed (4 bits per register) to indicate
 whether a register was, if referred to in any standard instructions,
-implicitly to be treated as a vector.  
+implicitly to be treated as a vector.
 
 Note:
 
@@ -860,7 +860,7 @@ levels: Base and reserved future functionality.
   up to 16 (TBD) of either the floating-point or integer registers to
   be marked as "predicated" (key), and if so, which integer register to
   use as the predication mask (value).
-  
+
 **TODO**
 
 # Implementing P (renamed to DSP) on top of Simple-V
@@ -1605,9 +1605,9 @@ would still be there (and stalled).  hmmm.
     >
     > Thrown away.
 
-discussion then led to the question of OoO architectures 
+discussion then led to the question of OoO architectures
 
-> The costs of the imprecise-exception model are greater than the benefit. 
+> The costs of the imprecise-exception model are greater than the benefit.
 > Software doesn't want to cope with it.  It's hard to debug.  You can't
 > migrate state between different microarchitectures--unless you force all
 > implementations to support the same imprecise-exception model, which would