nope. more repeated stuff, removed

diff --git a/svp64-primer/summary.tex b/svp64-primer/summary.tex
index 9a9f75f60bf8bae746b647bd514e50bb36efa48e..d71686a80fa4a90ebb853b20d7a674d29ad0e07f 100644 (file)
--- a/svp64-primer/summary.tex
+++ b/svp64-primer/summary.tex
@@ -178,24 +178,12 @@ Advantages include:
 \begin{itemize}
        \item Easy to create first (and sometimes only) implementation
              as a literal for-loop in hardware, simulators, and compilers.
-       \item Hardware Architects may understand and implement SV as
-          being an extra pipeline stage, inserted between decode and
-          issue. Essentially a simple for-loop issuing element-level
-          sub-instructions.
-       \item More complex HDL can be done by repeating existing scalar
-             ALUs and pipelines as blocks, leveraging existing Multi-Issue
-          Infrastructure.
-       \item Mostly high-level "context" which does not significantly
-          deviate from scalar Power ISA and, in its purest form
-          being a "for-loop around scalar instructions". Thus SV is
-          minimally-disruptive and consequently has a reasonable chance
-          of broad community adoption and acceptance.
        \item Obliterates SIMD opcode proliferation
           ($O(N^6)$) as well as dedicated Vectorisation
           ISAs. No more separate vector instructions.
        \item Reducing maintenance overhead (no separate Vector instructions).
-          Adding a Scalar instruction automatically gains a Vectorised
-          version.
+          Adding any new Scalar instruction
+          \textit{automatically adds a Vectorised version of the same}.
        \item Easier for compilers, coders, documentation
 \end{itemize}