Khronos' OpenCL Working Group has issued a Request for Proposal (#RFP) for OpenCL LLVM SPIR-V Backend. The goal of this project is to address and integrate specific functionalities that are currently available in the translator project but missing from the backend. All bids are due December 6, 2024.
Learn more: https://www.khronos.org/rfp/khronos-opencl-llvm-spir-v-backend
#LLVM #SPIRV #SPIR
Once @microsoft 's Shader Model 7 is released, #DirectX 12 will accept shaders compiled to SPIR-V. Microsoft is working with the Khronos #SPIR and #Vulkan Working Groups to ensure that this transition benefits the whole development ecosystem.
https://devblogs.microsoft.com/directx/directx-adopting-spir-v/
The #SPIR-V 1.6, Revision 3 specification is now available.
I should mention that this isn't just a matter of the dominant player intentionally boycotting standards that would make them lose the vendor lock-in advantage (hello #NVIDIA). All major vendors are guilty of this one way or the other. For example, #AMD unjustifiably pulled (or maybe failed to add) #SPIR and #CPU support from their new #OpenCL implementation. #Intel's #oneAPI (even while still leveraging the OpenCL backend) effectively failed on any other OpenCL platform.
@halcy
Former SPIR WG chair here.
It's "spear vee"
Mike Houston proposed the original SPIR at the January 2011 Khronos F2F. He gave it the name, expanded the acronym *and* was explicit about the pronunciation as "spear".
SPIR-V came later. Khronos has always pronounced it "spear vee"
That said, language is a living thing, so use what you like.
#Intel, #Arm & #Khronos Feel Ready to Land #SPIR-V Backend Within #LLVM
Based on
https://www.phoronix.com/scan.php?page=news_item&px=LLVM-Ready-For-SPIR-V-Backend
Original Source via mailing list
https://lists.llvm.org/pipermail/llvm-dev/2021-December/154270.html