From 1ddf359b7ca5ad4409bbb786d2485d4e94c562ab Mon Sep 17 00:00:00 2001 From: lkcl Date: Thu, 24 Dec 2020 06:10:52 +0000 Subject: [PATCH] --- openpower/sv/overview.mdwn | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/openpower/sv/overview.mdwn b/openpower/sv/overview.mdwn index e56043312..2d604aa2d 100644 --- a/openpower/sv/overview.mdwn +++ b/openpower/sv/overview.mdwn @@ -2,7 +2,8 @@ This document provides a crash-course overview as to why SV exists, and how it works. -SIMD is known to be 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. +[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. Cray-style variable-length Vectors on the other hand result in stunningly elegant and small loops 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. Unluke in SIMD powers of two limitations are not involved in either the hardware nor in the assembly code. -- 2.30.2