From 7992426adb5ea0c70d8992e3e05d55cd64cd7f3b Mon Sep 17 00:00:00 2001 From: lkcl Date: Thu, 24 Dec 2020 06:49:28 +0000 Subject: [PATCH] --- openpower/sv/overview.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openpower/sv/overview.mdwn b/openpower/sv/overview.mdwn index 6ce5edb3f..cf735aff4 100644 --- a/openpower/sv/overview.mdwn +++ b/openpower/sv/overview.mdwn @@ -3,7 +3,7 @@ This document provides a crash-course overview as to why SV exists, and how it works. [SIMD is known to be harmful](https://www.sigarch.org/simd-instructions-considered-harmful/): -a seductive simplicity that is easy to implement in hardware. Without predication, which is common only in 3D GPUs, realistically, at the time of writing (AVX512 came from Larrabee), SIMD widths only become more and more problematic. +a seductive simplicity that is easy to implement in hardware. Without predication, which is common only in 3D GPUs, SIMD only become more and more problematic as the SIMD width increases. Cray-style variable-length Vectors on the other hand result in stunningly elegant and small loops, with no alarmingly high setup and cleanup code, where at the hardware level the microarchitecture may execute from one element right the way through to tens of thousands at a time, yet the executable remains exactly the same. Unlike in SIMD, powers of two limitations are not involved in either the hardware nor in the assembly code. -- 2.30.2