From: pham.michael.98@a029fe8ac2da19fcd7269c492cf0410b2e5fd4cc Date: Sat, 14 Sep 2019 20:22:47 +0000 (+0100) Subject: Add in Khronos Standards X-Git-Tag: convert-csv-opcode-to-binary~4063 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=51a5823d8085fb519643d6395f8030a8b0deb6cd;p=libreriscv.git Add in Khronos Standards --- diff --git a/resources.mdwn b/resources.mdwn index 6a4d133a3..4bec4d9b5 100644 --- a/resources.mdwn +++ b/resources.mdwn @@ -18,6 +18,20 @@ Note: As far as I know, we aren't using the RISC-V V Extension directly at the m Almost all modern computers follow the IEEE Floating-Point Standard. Of course, we will follow it as well for interoperability. -* +* IEEE 754-2019: 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. + +# Khronos Standards + +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. + +* SPIR-V 1.5 Specification Revision 1: +* SPIR-V OpenCL Extended Instruction Set: +* SPIR-V GLSL Extended Instruction Set: +* Vulkan 1.1.122: +* OpenCL 2.2 API Specification: +* OpenCL 2.2 Extension Specification: +* OpenCL 2.2 SPIR-V Environment Specification: + +Note: I'm not sure what the plan is for OpenGL. Are we doing that in hardware or using Zink to run OpenGL on top of Vulkan?