(no commit message)

diff --git a/openpower/sv/rfc/ls001.mdwn b/openpower/sv/rfc/ls001.mdwn
index 234b3f4b18c737d4379a0161015c5a693a15d198..9d5b98a109531a63af7e1d6ff3f2233181c8fc12 100644 (file)
--- a/openpower/sv/rfc/ls001.mdwn
+++ b/openpower/sv/rfc/ls001.mdwn
@@ -387,16 +387,19 @@ The biggest advantage inherent in Vertical-First is that it is very easy
 to introduce into compilers, because all looping, as far as programs
 is concerned, remains expressed as *Scalar assembler*.[^autovec]
 Whilst Mitch Alsup's
-VVM advocates auto-vectorisation and is limited in its ability to call
+VVM biggest strength is its hardware-level auto-vectorisation
+but is limited in its ability to call
 functions, Simple-V's Vertical-First provides explicit control over the
 parallelism ("hphint")[^hphint] and also allows for full state to be stored/restored
-(SVLR combined with LR), permitting full function calls to be made.
+(SVLR combined with LR), permitting full function calls to be made
+from inside Vertical-First Loops, and potentially allows arbitrarily-depth
+nested VF Loops.
 
 Simple-V Vertical-First Looping requires an explicit instruction to
 move `SVSTATE` regfile offsets forward: `svstep`. An early version of 
 Vectorised
 Branch-Conditional attempted to merge the functionality of `svstep`
-into `sv.bc`: it became CISC-like and was reverted.
+into `sv.bc`: it became CISC-like in its complexity and was quickly reverted.
 
 \newpage{}
 # Simple-V REMAP subsystem