that makes a truly ubiquitous Vector ISA) in ways that will become apparent
over time as adoption increases. In the meantime programmers are, in
direct violation of ARM's advice on how to use SVE2, trying desperately
-to use it as if it was Packed SIMD NEON.
+to use it as if it was Packed SIMD NEON. The advice not to create SVE2
+assembler that is hardcoded to fixed widths is being disregarded, in
+favour of writing *multiple identical implementations* of a function,
+each with a different hardware width, and compelling software to choose
+one at runtime after probing the hardware.
Even RISC-V, for all that we can be grateful to the RISC-V Founders for
-reviving Cray Vectors, has severe performance and imolementation
+reviving Cray Vectors, has severe performance and implementation
limitations that are only really apparent to exceptionally experienced
assembly-level developers with a wide, diverse depth in multiple ISAs:
one of the best and clearest is a
its use in low-performance embedded scenarios is not ideal: in
private custom secretive commercial usage it is perfect. Ubiquitous
and common everyday usage in scenarios currently occupied by ARM, Intel,
-AMD and IBM: not so much. Thus, even though RISC-V has Cray-style Vectors,
-the ISA is, unfortunately, fundamentally flawed.
+AMD and IBM? not so much. Thus, even though RISC-V has Cray-style Vectors,
+the whole ISA is, unfortunately, fundamentally flawed as far as power
+efficient high performance is concerned.
+
+Slowly, at this point, a realisation should be sinking in that, actually,
+there aren't as many really truly viable Vector ISAs out there, as the
+ones that are evolving in the general direction of Vectorisation are,
+in various completely different ways, flawed.