(no commit message)

diff --git a/openpower/sv/overview.mdwn b/openpower/sv/overview.mdwn
index 0a93bd1c9097331bbfd14b61afaac5368e8d9a12..f87e7e98bc49f8395d206aea1a6798fb91e25ada 100644 (file)
--- a/openpower/sv/overview.mdwn
+++ b/openpower/sv/overview.mdwn
@@ -26,7 +26,7 @@ The fundamentals are:
 * Once the loop is completed *only then* is the Program Counter
   allowed to move to the next instruction.
 
-Hardware (and simulator) implementors are free and clear to implement this as literally a for-loop, sitting in between instruction decode and issue.  Higher performance systems may deploy SIMD backends and multi-issue, although it is strongly recommended to add predication capability into all SIMD backend units.
+Hardware (and simulator) implementors are free and clear to implement this as literally a for-loop, sitting in between instruction decode and issue.  Higher performance systems may deploy SIMD backends, multi-issue and out-of-order execution, although it is strongly recommended to add predication capability into all SIMD backend units.
 
 In OpenPOWER ISA v3.0B pseudo-code form, an ADD operation, assuming both source and destination have been "tagged" as Vectors, is simply: