Mastodon

David Neto<a href="https://mastodon.social/@pervognsen" class="u-url mention" rel="nofollow noopener" target="_blank">@pervognsen</a> We're probably on the same page about formal methods.I wanted to point out a cool example I helped with: formalizing the structured control flow rules for SPIR-V.<a href="https://dl.acm.org/doi/10.1145/3571253" rel="nofollow noopener" translate="no" target="_blank">https://dl.acm.org/doi/10.1145/3571253</a>This was a really nice blend of theory and practice to nail the details on a gnarly bit of the GPU intermediate language we know and love. And in the end the (prose) rules are easier to understand too.<a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a>

David NetoThere are now 48 registered SPIR-V generator tools.Woohoo.<a href="https://github.com/KhronosGroup/SPIRV-Headers/blob/main/include/spirv/spir-v.xml#L100" rel="nofollow noopener" translate="no" target="_blank">https://github.com/KhronosGroup/SPIRV-Headers/blob/main/include/spirv/spir-v.xml#L100</a><a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://mastodon.gamedev.place/tags/khronosgroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#khronosgroup</a>

Giuseppe BilottaI'm getting the material ready for my upcoming <a href="https://fediscience.org/tags/GPGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPGPU</a> course that starts on March. Even though I most probably won't get to it,I also checked my trivial <a href="https://fediscience.org/tags/SYCL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SYCL</a> programs. Apparently the 2025.0 version of the <a href="https://fediscience.org/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://fediscience.org/tags/OneAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OneAPI</a> <a href="https://fediscience.org/tags/DPCPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#DPCPP</a> runtime doesn't like any <a href="https://fediscience.org/tags/OpenCL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenCL</a> platform except Intel's own (I have two other platforms that support <a href="https://fediscience.org/tags/SPIRV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPIRV</a>, so why aren't they showing up? From the documentation I can find online this should be sufficient, but apparently it's not …)

Ben AshbaughI've been writing quite a few SPIR-V modules by hand for testing lately. It's tolerable, but only barely.My primary complaints are:1. Verbosity. A test for a single instruction tends to be at least 20 lines and sometimes much more. 2. SSA is great for compilers, not so much for humans. 3. Getting all of the type declarations and capabilities right is annoying.Is there a better way? <a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a>

David NetoVulkan 1.4:Glslang, Shaderc, and SPIRV-Tools updates have landed to be able to target Vulkan 1.4. No major changes to Vulkan SPIR-V, so this is mostly about being able to specify Vulkan 1.4 in options lists.These will be rolled into the next Vulkan SDK.<a href="https://mastodon.gamedev.place/tags/vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulkan</a> <a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a>

Khronos GroupKhronos' OpenCL Working Group has issued a Request for Proposal (<a href="https://fosstodon.org/tags/RFP" class="mention hashtag" rel="nofollow noopener" target="_blank">#RFP</a>) 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: <a href="https://www.khronos.org/rfp/khronos-opencl-llvm-spir-v-backend" rel="nofollow noopener" translate="no" target="_blank">https://www.khronos.org/rfp/khronos-opencl-llvm-spir-v-backend</a> <a href="https://fosstodon.org/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> <a href="https://fosstodon.org/tags/SPIRV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPIRV</a> <a href="https://fosstodon.org/tags/SPIR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPIR</a>

SiebencorgieThe rust-gpu project now has two more maintainers. Happy to see the project gaining speed!I'm using rust-gpu for most my Vulkan experiments these days. It's one of the enablers of my SDF-compiler toolchain. It lets you define linking points, which in turn allows me to link my SDF generated SPIR-V code into rust-gpu generated SPIR-V modules.<a href="https://rust-gpu.github.io/blog/2024/11/06/new-maintainers/" rel="nofollow noopener" translate="no" target="_blank">https://rust-gpu.github.io/blog/2024/11/06/new-maintainers/</a><a href="https://mastodon.gamedev.place/tags/gamedev" class="mention hashtag" rel="nofollow noopener" target="_blank">#gamedev</a> <a href="https://mastodon.gamedev.place/tags/cc" class="mention hashtag" rel="nofollow noopener" target="_blank">#cc</a> <a href="https://mastodon.gamedev.place/tags/compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#compilers</a> <a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://mastodon.gamedev.place/tags/vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulkan</a> <a href="https://mastodon.gamedev.place/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> <a href="https://mastodon.gamedev.place/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a>

LukasDirectX is adopting SPIR-V 🤯<a href="https://devblogs.microsoft.com/directx/directx-adopting-spir-v/" rel="nofollow noopener" translate="no" target="_blank">https://devblogs.microsoft.com/directx/directx-adopting-spir-v/</a><a href="https://swiss.social/tags/directx" class="mention hashtag" rel="nofollow noopener" target="_blank">#directx</a> <a href="https://swiss.social/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://swiss.social/tags/khronos" class="mention hashtag" rel="nofollow noopener" target="_blank">#khronos</a> <a href="https://swiss.social/tags/gamedev" class="mention hashtag" rel="nofollow noopener" target="_blank">#gamedev</a>

aliaFinally got <a href="https://sunny.garden/tags/HLSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#HLSL</a> -> <a href="https://sunny.garden/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> -> running in <a href="https://sunny.garden/tags/bevy" class="mention hashtag" rel="nofollow noopener" target="_blank">#bevy</a>! Just a simple compute shader for slope/normal/ocean detection at the moment. The spirv inpsector at <a href="https://www.khronos.org/spir/visualizer/" rel="nofollow noopener" translate="no" target="_blank">https://www.khronos.org/spir/visualizer/</a> was a life saver! also, this is the first time ive use the build.rs in <a href="https://sunny.garden/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> suuuper handy for automatically recompiling the hlsl. Feels like bevy's Dx12 backend might need some love since i had to switch back to vulcan but so happy to have actually got it running.

David NetoI think people get tied up in knots when trying to parse SPIR-V with structured control flow.You gotta do it in reverse structured post-order.Once you lay out the basic blocks in that order, the nested control constructs map to *intervals* over that list. (:galaxy brain:)For details, see Tint's SPIR-V to WGSL translator.<a href="https://dawn.googlesource.com/dawn/+/refs/heads/main/src/tint/lang/spirv/reader/ast_parser/function.cc#72" rel="nofollow noopener" translate="no" target="_blank">https://dawn.googlesource.com/dawn/+/refs/heads/main/src/tint/lang/spirv/reader/ast_parser/function.cc#72</a><a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://mastodon.gamedev.place/tags/vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulkan</a> <a href="https://mastodon.gamedev.place/tags/wgsl" class="mention hashtag" rel="nofollow noopener" target="_blank">#wgsl</a> <a href="https://mastodon.gamedev.place/tags/webgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#webgpu</a>

I HAVE MOVEDDoes anyone know whether <a href="https://functional.cafe/tags/SpirV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpirV</a> supports closures?By the spec, it seems like I can define a function inside a function. Can the outer function return a pointer to the inner function?And since we're here, is there a dedicated forum/community/chat where I can ask this kinds of questions? The Khronos SPIR forum seems dead. =|

David Neto<a href="https://fosstodon.org/@ypujante" class="u-url mention" rel="nofollow noopener" target="_blank">@ypujante</a> (And, those would be one of the unit tests of the SPIR-V to WGSL translator, converted to an end-to-end test so we can check the right thing will be emitted on all the backend languages.)<a href="https://mastodon.gamedev.place/tags/webgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#webgpu</a> <a href="https://mastodon.gamedev.place/tags/tint" class="mention hashtag" rel="nofollow noopener" target="_blank">#tint</a> <a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://mastodon.gamedev.place/tags/wgsl" class="mention hashtag" rel="nofollow noopener" target="_blank">#wgsl</a> <a href="https://mastodon.gamedev.place/tags/da" class="mention hashtag" rel="nofollow noopener" target="_blank">#da</a>

I HAVE MOVED<pre><code>mkdir src/Targets/SpirV </code></pre>It's happening.... _^I'm finally starting the work to compile <a href="https://functional.cafe/tags/Squarepants" class="mention hashtag" rel="nofollow noopener" target="_blank">#Squarepants</a> to <a href="https://functional.cafe/tags/SpirV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpirV</a>... I never thought my language would get to this point! =D =D =D<a href="https://functional.cafe/tags/FunctionalProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#FunctionalProgramming</a> <a href="https://functional.cafe/tags/graphics" class="mention hashtag" rel="nofollow noopener" target="_blank">#graphics</a>

I HAVE MOVEDI'm finally at the point where I have to start working on perhaps the main feature of my programming language Squarepants: the ability to compile to GPU Shaders.The most attractive target would be <a href="https://functional.cafe/tags/SpirV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpirV</a> which is an intermediate representation that works almost everywhere... Except on browsers, and only because <a href="https://functional.cafe/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> didn't want to give control of the standard to the group that develops SpirV. Instead, Apple imposed <a href="https://functional.cafe/tags/WGSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#WGSL</a> , which is a language instead than an intermediate representation, so it's a pain in the ass to target and will end up with the same problem as <a href="https://functional.cafe/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> .At some point there will be translators from SpirV to WGSL, but I can't rely on those now.So, what am I going to target? Right now Squarepants compiles to javascript, so can run easily in both browsers and <a href="https://functional.cafe/tags/nodejs" class="mention hashtag" rel="nofollow noopener" target="_blank">#nodejs</a>.There is a project to run SpirV (via Vulkan) on node, but has been dead for years, which means that if I want to compile to a native application, I need Squarepants to compile to C or LLVM first.OTOH if I go through the square-peg-in-round-hole and target WGSL, then I can target browsers.-sigh-, I feel like I have no good option.

Julien BarnoinI know SPIR-V is not meant for human readability and all that, but damn. Is there not any way that the variables were named anything closer to useful than %13525? I understand that it's not a one-to-one match with my glsl variables, but like... This feels like it's actively trying to obfuscate the code 🥲Maybe there's some glslang option I don't know about that tries to make them a bit clearer?<a href="https://mastodon.gamedev.place/tags/glsl" class="mention hashtag" rel="nofollow noopener" target="_blank">#glsl</a> <a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://mastodon.gamedev.place/tags/vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulkan</a> <a href="https://mastodon.gamedev.place/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.gamedev.place/tags/gamedev" class="mention hashtag" rel="nofollow noopener" target="_blank">#gamedev</a>

VulkanThe SPIR Working Group developed 2 new SPIR-V extensions to provide shader authors with more guarantees about the execution model of shaders: SPV_KHR_maximal_reconvergence and VK_KHR_shader_quad_control.Learn more: <a href="https://www.khronos.org/blog/khronos-releases-maximal-reconvergence-and-quad-control-extensions-for-vulkan-and-spir-v" rel="nofollow noopener" translate="no" target="_blank">https://www.khronos.org/blog/khronos-releases-maximal-reconvergence-and-quad-control-extensions-for-vulkan-and-spir-v</a> <a href="https://fosstodon.org/tags/SPIRV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPIRV</a> <a href="https://fosstodon.org/tags/Vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vulkan</a> <a href="https://fosstodon.org/tags/Shaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shaders</a>

SiebencorgieMy small SDF language is working now!It currently compiles this code in ~5ms into a new SPIR-V module that is linked into the sphere-tracing shader. The `offset` parameter is wired to a push constant. So you can move the sphere/torus in this example without having to recompile the SDF.<a href="https://mastodon.gamedev.place/tags/compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#compilers</a> <a href="https://mastodon.gamedev.place/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://mastodon.gamedev.place/tags/langdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#langdev</a> <a href="https://mastodon.gamedev.place/tags/vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulkan</a> <a href="https://mastodon.gamedev.place/tags/sdf" class="mention hashtag" rel="nofollow noopener" target="_blank">#sdf</a>

blake shaw 🇵🇸wow this project is so cool, a sophisticated <a href="https://functional.cafe/tags/shader" class="mention hashtag" rel="nofollow noopener" target="_blank">#shader</a> IDE with its own <a href="https://functional.cafe/tags/SPIRV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPIRV</a> virtual machine <a href="https://shadered.org/" rel="nofollow noopener" translate="no" target="_blank">https://shadered.org/</a> <a href="https://github.com/dfranx/SPIRV-VM" rel="nofollow noopener" translate="no" target="_blank">https://github.com/dfranx/SPIRV-VM</a><a href="https://functional.cafe/tags/glsl" class="mention hashtag" rel="nofollow noopener" target="_blank">#glsl</a>

Pekka JääskeläinenchipStar 1.0 released! It's a tool for compiling and running CUDA/HIP applications on SPIR-V-supported OpenCL or LevelZero platforms. v1.0 can already run various HPC applications correctly. See: <a href="https://github.com/CHIP-SPV/chipStar/releases/tag/v1.0" rel="nofollow noopener" target="_blank">https://github.com/CHIP-SPV/chipStar/releases/tag/v1.0</a> <a href="https://fosstodon.org/tags/opencl" class="mention hashtag" rel="nofollow noopener" target="_blank">#opencl</a> <a href="https://fosstodon.org/tags/levelzero" class="mention hashtag" rel="nofollow noopener" target="_blank">#levelzero</a> <a href="https://fosstodon.org/tags/spirv" class="mention hashtag" rel="nofollow noopener" target="_blank">#spirv</a> <a href="https://fosstodon.org/tags/cuda" class="mention hashtag" rel="nofollow noopener" target="_blank">#cuda</a> <a href="https://fosstodon.org/tags/hip" class="mention hashtag" rel="nofollow noopener" target="_blank">#hip</a>

Giuseppe BilottaAt the very least, this could give us support for <a href="https://fediscience.org/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> hardware, and, at least in theory, potentially any device with <a href="https://fediscience.org/tags/OpenCL2" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenCL2</a> and <a href="https://fediscience.org/tags/SPIRV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPIRV</a> support —such as the Mali GPU on my phone! I would be very curious to test the performance on it compared to the CPU of the same device.

Recent searches

Search options

Administered by:

Server stats:

#spirv