Additional references at the request of Luke
[libreriscv.git] / resources.mdwn
1 # Resources and Specifications
2
3 This page aims to collect all the resources and specifications we need in one place for quick access. We will try our best to keep links here up-to-date. Feel free to add more links here.
4
5 # RISC-V Instruction Set Architecture
6
7 The Libre RISC-V Project is building a hybrid CPU/GPU SoC. As the name of the project implies, we will be following the RISC-V ISA due to it being open-source and also because of the huge software and hardware ecosystem building around it. There are other open-source ISAs but none of them have the same momentum and energy behind it as RISC-V.
8
9 To fully take advantage of the RISC-V ecosystem, it is important to be compliant with the RISC-V standards. Doing so will allow us to to reuse most software as-is and avoid major forks.
10
11 * Official compiled PDFs of RISC-V ISA Manual: <https://github.com/riscv/riscv-isa-manual/releases/latest>
12 * Working draft of the proposed RISC-V Bitmanipulation extension: <https://github.com/riscv/riscv-bitmanip/blob/master/bitmanip-draft.pdf>
13 * RISC-V "V" Vector Extension: <https://riscv.github.io/documents/riscv-v-spec/>
14
15 Note: As far as I know, we aren't using the RISC-V V Extension directly at the moment. However, there are many wiki pages that make a reference to the V extension so it would be good to include it here as a reference for comparative/informative purposes with regard to Simple-V.
16 # IEEE Standard for Floating-Point Arithmetic (IEEE 754)
17
18 Almost all modern computers follow the IEEE Floating-Point Standard. Of course, we will follow it as well for interoperability.
19
20 * IEEE 754-2019: <https://standards.ieee.org/standard/754-2019.html>
21
22 Note: Even though this is such an important standard used by everyone, it is unfortunately not freely available and requires a payment to access. However, each of the Libre RISC-V members already have access to the document.
23
24 # Khronos Standards
25
26 The Khronos Group creates open standards for authoring and acceleration of graphics, media, and computation. It is a requirement for our hybrid CPU/GPU to be compliant with these standards, especially Vulkan and OpenCL being the most important. SPIR-V is also important for the Kazan driver.
27
28 **SPIR-V Main Page <https://www.khronos.org/registry/spir-v/>**
29
30 * SPIR-V 1.5 Specification Revision 1: <https://www.khronos.org/registry/spir-v/specs/unified1/SPIRV.html>
31 * SPIR-V OpenCL Extended Instruction Set: <https://www.khronos.org/registry/spir-v/specs/unified1/OpenCL.ExtendedInstructionSet.100.html>
32 * SPIR-V GLSL Extended Instruction Set: <https://www.khronos.org/registry/spir-v/specs/unified1/GLSL.std.450.html>
33
34 **Vulkan Main Page <https://www.khronos.org/registry/vulkan/>**
35
36 * Vulkan 1.1.122: <https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/index.html>
37
38 **OpenCL Main Page <https://www.khronos.org/registry/OpenCL/>**
39
40 * OpenCL 2.2 API Specification: <https://www.khronos.org/registry/OpenCL/specs/2.2/html/OpenCL_API.html>
41 * OpenCL 2.2 Extension Specification: <https://www.khronos.org/registry/OpenCL/specs/2.2/html/OpenCL_Ext.html>
42 * OpenCL 2.2 SPIR-V Environment Specification: <https://www.khronos.org/registry/OpenCL/specs/2.2/html/OpenCL_Env.html>
43
44 Note: We are implementing hardware accelerated Vulkan (and possibly OpenCL) while relying on other software projects to translate APIs to Vulkan. E.g. Zink allows for OpenGL-->Vulkan in software.
45
46 # Graphics and Compute API Stack
47
48 I found this informative post that mentions Kazan and a whole bunch of other stuff. It looks like *many* APIs can be emulated on top of Vulkan, although performance is not evaluated.
49
50 <https://synappsis.wordpress.com/2017/06/03/opengl-over-vulkan-dev/>
51
52 # Free Silicon Conference
53
54 The conference brought together experts and enthusiasts who want to build a complete Free and Open Source CAD ecosystem for designing analog and digital integrated circuits.
55 The conference covered the full spectrum of the design process, from system architecture, to layout and verification.
56
57 <https://wiki.f-si.org/index.php/FSiC2019#Foundries.2C_PDKs_and_cell_libraries>
58
59 LIP6's Coriolis - a set of backend design tools: <https://www-soc.lip6.fr/equipe-cian/logiciels/coriolis/>
60
61 Note: The rest of LIP6's website is in French, but there is a UK flag in the corner that gives the English version.
62
63 KLayout - Layout viewer and editor: <https://www.klayout.de/>
64
65 # The OpenROAD Project
66
67 OpenROAD seeks to develop and foster an autonomous, 24-hour, open-source layout generation flow (RTL-to-GDS).
68
69 <https://theopenroadproject.org/>