3 # Simple-V Vectorisation for the OpenPOWER ISA
5 **SV is in DRAFT STATUS**. SV has not yet been submitted to the OpenPOWER Foundation ISA WG for review.
7 <https://bugs.libre-soc.org/show_bug.cgi?id=213>
9 Fundamental design principles:
11 * Simplicity of introduction and implementation on the existing OpenPOWER ISA
12 * Effectively a hardware for-loop, pausing PC, issuing multiple scalar operations
13 * Preserving the underlying scalar execution dependencies as if the for-loop had been expanded as actual scalar instructions
14 (termed "preserving Program Order")
15 * Augments ("tags") existing instructions, providing Vectorisation "context" rather than adding new ones.
16 * Does not modify or deviate from the underlying scalar OpenPOWER ISA unless it provides significant performance or other advantage to do so in the Vector space (dropping XER.SO and OE=1 for example)
17 * Designed for Supercomputing: avoids creating significant sequential
18 dependency hazards, allowing high performance superscalar microarchitectures to be deployed.
20 Advantages of these design principles:
22 * It is therefore easy to create a first (and sometimes only) implementation as literally a for-loop in hardware, simulators, and compilers.
23 * More complex HDL can be done by repeating existing scalar ALUs and pipelines as blocks.
24 * As (mostly) a high-level "context" that does not (significantly) deviate from scalar OpenPOWER ISA and, in its purest form being "a for loop around scalar instructions", it is minimally-disruptive and consequently stands a reasonable chance of broad community adoption and acceptance
25 * Completely wipes not just SIMD opcode proliferation off the
26 map (SIMD is O(N^6) opcode proliferation)
27 but off of Vectorisation ISAs as well. No more separate Vector
30 Pages being developed and examples
32 * [[sv/overview]] explaining the basics.
33 * [[sv/implementation]] implementation planning and coordination
34 * [[sv/svp64]] contains the packet-format *only*
35 * [[sv/setvl]] the Cray-style "Vector Length" instruction
36 * [[sv/predication]] discussion on predication concepts
37 * [[sv/cr_int_predication]] instructions needed for effective predication
38 * [[opcode_regs_deduped]]
39 * [[sv/vector_swizzle]]
41 * [[sv/register_type_tags]]
44 * [[sv/branches]] - SVP64 Conditional Branch behaviour: All/Some Vector CRs
45 * [[sv/cr_ops]] - SVP64 Condition Register ops: Guidelines
46 on Vectorisation of any v3.0B base operations which return
47 or modify a Condition Register bit or field.
48 * [[sv/fcvt]] FP Conversion (due to OpenPOWER Scalar FP32)
49 * [[sv/fclass]] detect class of FP numbers
50 * [[sv/int_fp_mv]] Move and convert GPR <-> FPR, needed for !VSX
51 * [[sv/mv.vec]] move to and from vec2/3/4
52 * [[sv/ldst]] Load and Store
55 * [[sv/biginteger]] Operations that help with big arithmetic
56 * [[sv/remap]] "Remapping" for Matrix Multiply and RGB "Structure Packing"
57 * [[sv/svstep]] Key stepping instruction for Vertical-First Mode
58 * [[sv/propagation]] Context propagation including svp64, swizzle and remap
59 * [[sv/vector_ops]] Vector ops needed to make a "complete" Vector ISA
60 * [[sv/av_opcodes]] scalar opcodes for Audio/Video
61 * Twin targetted instructions (two registers out, one implicit)
62 Explanation of the rules for twin register targets
63 (implicit RS, FRS) explained in SVP4 [[sv/svp64/appendix]]
64 - [[isa/svfixedarith]]
66 * TODO: OpenPOWER [[openpower/transcendentals]]
68 Examples ideas discussion:
70 * [[sv/masked_vector_chaining]]
72 * [[sv/example_dep_matrices]]
73 * [[sv/major_opcode_allocation]]
75 * [[sv/16_bit_compressed]] experimental
76 * [[sv/toc_data_pointer]] experimental
80 * <https://www.sigarch.org/simd-instructions-considered-harmful/>
81 * [[simple_v_extension]] old (deprecated) version
82 * [[openpower/sv/llvm]]
83 * [[openpower/sv/effect-of-more-decode-stages-on-reg-renaming]]
87 Required Background Reading:
88 ============================
90 These are all, deep breath, basically... required reading, *as well as and in addition* to a full and comprehensive deep technical understanding of the Power ISA, in order to understand the depth and background on SVP64 as a 3D GPU and VPU Extension.
92 I am keenly aware that each of them is 300 to 1,000 pages (just like the Power ISA itself).
94 This is just how it is.
96 Given the sheer overwhelming size and scope of SVP64 we have gone to CONSIDERABLE LENGTHS to provide justification and rationalisation for adding the various sub-extensions to the Base Scalar Power ISA.
98 * Scalar bitmanipulation is justifiable for the exact same reasons the extensions are justifiable for other ISAs. The additional justification for their inclusion where some instructions are already (sort-of) present in VSX is that VSX is not mandatory, and the complexity of implementation of VSX is too high a price to pay at the Embedded SFFS Compliancy Level.
100 * Scalar FP-to-INT conversions, likewise. ARM has a javascript conversion instruction, Power ISA does not (and it costs a ridiculous 45 instructions to implement, including 6 branches!)
102 * Scalar Transcendentals (SIN, COS, ATAN2, LOG) are easily justifiable for High-Performance Compute workloads.
104 It also has to be pointed out that normally this work would be covered by multiple separate full-time Workgroups with multiple Members contributing their time and resources!
106 Overall the contributions that we are developing take the Power ISA out of the specialist highly-focussed market it is presently best known for, and expands it into areas with much wider general adoption and broader uses.
111 OpenCL specifications are linked here, these are relevant when we get to a 3D GPU / High Performance Compute ISA WG RFC:
112 [[openpower/transcendentals]]
114 (Failure to add Transcendentals to a 3D GPU is directly equivalent to *willfully* designing a product that is 100% destined for commercial failure.)
116 I mention these because they will be encountered in every single commercial GPU ISA, but they're not part of the "Base" (core design) of a Vector Processor. Transcendentals can be added as a sub-RFC.
120 Actual 3D GPU Architectures and ISAs:
121 -------------------------------------
124 <https://github.com/hermanhermitage/videocoreiv>
127 <https://github.com/etnaviv/etna_viv/tree/master/doc>
130 <http://www.cs.binghamton.edu/~millerti/nyuziraster.pdf>
133 <https://github.com/cwabbott0/mali-isa-docs>
136 <https://developer.amd.com/wp-content/resources/RDNA_Shader_ISA.pdf>
137 <https://developer.amd.com/wp-content/resources/Vega_Shader_ISA_28July2017.pdf>
139 * MIAOW which is *NOT* a 3D GPU, it is a processor which happens to implement a subset of the AMDGPU ISA (Southern Islands), aka a "GPGPU"
140 <https://miaowgpu.org/>
143 Actual Vector Processor Architectures and ISAs:
144 -----------------------------------------------
147 <https://www.hpc.nec/documents/guide/pdfs/Aurora_ISA_guide.pdf>
150 <http://www.bitsavers.org/pdf/cray/CRAY_Y-MP/HR-04001-0C_Cray_Y-MP_Computer_Systems_Functional_Description_Jun90.pdf>
153 <https://github.com/riscv/riscv-v-spec>
155 * MRISC32 ISA Manual (under active development)
156 <https://github.com/mrisc32/mrisc32/tree/master/isa-manual>
158 * Mitch Alsup's MyISA 66000 Vector Processor ISA Manual is available from Mitch on direct contact with him. It is a different approach from the others, which may be termed "Cray-Style Horizontal-First" Vectorisation. 66000 is a *Vertical-First* Vector ISA.
160 The term Horizontal or Vertical alludes to the Matrix "Row-First" or "Column-First" technique, where:
162 * Horizontal-First processes all elements in a Vector before moving on to the next instruction
163 * Vertical-First processes *ONE* element per instruction, and requires loop constructs to explicitly step to the next element.
165 Vector-type Support by Architecture
167 Architecture | Horizontal | Vertical
179 <img src="https://assets.amuniversal.com/7fada35026ca01393d3d005056a9545d" width="600" />