Spirv tagged stories

Spirv tagged stories

Updates from OpenCL Tooling Task Sub Group: Recently Upstreamed SPIR-V Backend Ready for Discussion at 2022 LLVM Developers’ Meeting

OpenCL™ Tooling Task Sub Group (TSG) is actively contributing to the LLVM compiler infrastructure project and is determined to bring first-class support for OpenCL and SPIR-V™ to LLVM. While the latest release of Clang brought the long-awaited support for the OpenCL 3.0 standard, C++ for OpenCL 2021 kernel language, and the SPIR-V generation interface utilizing an external tool llvm-spirv from the SPIRV-LLVM-Translator repository, t

Catching Up with Khronos: Experts’ Q&A on OpenCL 3.0 and SYCL 2020

Recently, Simon McIntosh-Smith talked with a group of OpenCL and SYCL subject matter experts about the recent announcements of OpenCL 3.0 and the SYCL 2020 provisional release. Here’s a recap of Simon McIntosh-Smith’s discussion with these experts, where they walk us through the newest events.

Khronos’ OpenCL, SYCL, and SPIR-V Standards Find Growing Synergy with LLVM’s Compiler Community

The Khronos® OpenCL™ working group recently created a new Tooling Subgroup with the aim of improving the tools ecosystem for this widely-used open standard for heterogeneous computation—in particular, boosting the development of tooling components that can be shared by multiple vendors. Subgroup members have been meeting regularly to coordinate the overall direction for OpenCL tools, with an emphasis on strengthening the development of tools in open source, particularly by encouraging collaboration between the OpenCL and LLVM communities.

Vulkan has just become the world’s first graphics API with a formal memory model.  So, what is a memory model and why should I care?

Khronos has released a provisional Vulkan Memory Model Specification that includes extensions for Vulkan, SPIR-V, and GLSL and gives Vulkan developers additional control over how their shaders synchronize access to should cooperate safely over memory operations in a parallel execution environment. In tandem with the extension specification, Khronos has released memory model extension conformance tests to enable implementers to do early tests on their shader compilers to ensure that the specified memory synchronization is implemented correctly. The memory model will have an Alloy description of the extension functionality to enable formal modeling and experimentation.