#spirv — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #spirv, aggregated by home.social.
-
OpenCL 3.1 is here.
The Khronos Group has moved several capabilities into the core spec, including SPIR-V kernels, subgroups, and integer dot products.
Also includes improvements to the memory model and synchronization, plus better alignment with Vulkan via device UUID queries.
Implementations are already underway across major vendors and open source projects.
- Full Blog: https://www.khronos.org/blog/opencl-3.1-is-here?utm_medium=social&utm_source=mastodon&utm_campaign=OpenCL_3.1_is_here&utm_content=blog
- OpenCL specification GitHub
- Khronos Discord -
The IWOCL 2026 program is live!
The 14th International Workshop on OpenCL and SYCL is coming to Heilbronn, Germany this May 6–8, and the full conference program has just been published at iwocl.org.
This year's lineup is packed. Whether you're working on heterogeneous HPC, GPU portability, or the future of open compute standards, this is the event for you.
Explore the program at https://www.iwocl.org/iwocl-2026/conference-program/
#SYCL #OpenCL #Khronos #SPIRV #IWOCL2026 #HighPerformanceComputing #HPC #GPU -
We're excited to announce that the slides and videos from the inaugural Shading Languages Symposium are now available! Catch up on all the proceedings and join us next year!
https://www.khronos.org/events/shading-languages-symposium-2026
#shading #shaders #programming #Slang #GLSL #HLSL #SPIRV #glslang #WESL #WGSL #OSL #Gigi #vkDuck -
We're excited to announce that the slides and videos from the inaugural Shading Languages Symposium are now available! Catch up on all the proceedings and join us next year!
https://www.khronos.org/events/shading-languages-symposium-2026
#shading #shaders #programming #Slang #GLSL #HLSL #SPIRV #glslang #WESL #WGSL #OSL #Gigi #vkDuck -
We're excited to announce that the slides and videos from the inaugural Shading Languages Symposium are now available! Catch up on all the proceedings and join us next year!
https://www.khronos.org/events/shading-languages-symposium-2026
#shading #shaders #programming #Slang #GLSL #HLSL #SPIRV #glslang #WESL #WGSL #OSL #Gigi #vkDuck -
We're excited to announce that the slides and videos from the inaugural Shading Languages Symposium are now available! Catch up on all the proceedings and join us next year!
https://www.khronos.org/events/shading-languages-symposium-2026
#shading #shaders #programming #Slang #GLSL #HLSL #SPIRV #glslang #WESL #WGSL #OSL #Gigi #vkDuck -
We are very excited for next week's Shading Language Symposium in San Diego!
This event will bring together graphics and computer shader programmers, researchers and technical artists with shading language implementers to explore the landscape of shading languages, their future development, and the role how new techniques such as neural graphics will play in shaping the future of real-time rendering.
Learn more: https://www.khronos.org/events/shading-languages-symposium-2026
#glsl #hlsl #osl #slang #spirv #wgsl -
Khronos announced the inaugural Shading Languages Symposium, that will take place on February 12-13, 2026, in San Diego, California. The symposium will bring together developers, implementors, researchers, and technical artists to explore the current state and future development of #shading languages and real-time #rendering technologies. The open call for submissions for the symposium closes on October 12, 2025.
-
I'm getting the material ready for my upcoming #GPGPU course that starts on March. Even though I most probably won't get to it,I also checked my trivial #SYCL programs. Apparently the 2025.0 version of the #Intel #OneAPI #DPCPP runtime doesn't like any #OpenCL platform except Intel's own (I have two other platforms that support #SPIRV, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)
-
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 -
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 -
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 -
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 -
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 -
@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.
-
@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.
-
@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.
-
@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.
-
@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.