SPIRV-Cross
ssgl
Our great sponsors
SPIRV-Cross | ssgl | |
---|---|---|
10 | 13 | |
1,905 | 68 | |
1.9% | - | |
9.0 | 2.1 | |
8 days ago | 4 months ago | |
GLSL | C | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SPIRV-Cross
-
Why aren't there constantly more shading languages popping up all the time like other languages?
There also exists something like SPIRV-Cross which promises to be able to generate code from the SPIRV intermediate representation into Metal and all versions of GLSL and HLSL. I am not sure really how good it is at this point, but going forward we might start to see more high-level shader languages, that compile to SPRIV and then from there to the myriad of different shader formats different platforms expect.
-
The trouble with SPIR-V, 2022 edition
If you have shaders, I believe you can use SPIRV-Cross to generate GLSL, which you can probably get to pass as OpenCL C with just a bunch of macro tweaks, or at worst some small changes to spv-cross.
-
Need guidance on SPIRV reflection
Regarding reflection, here is a guide: https://github.com/KhronosGroup/SPIRV-Cross/wiki/Reflection-API-user-guide
-
What are your (dynamic) shader workflows when targeting multiple backends (Vulkan and Metal)?
I am working on an engine that targets Vulkan and Metal. I'm at the point now where I want to be able to dynamically update my shader at runtime to suit the type of data being sent in for drawing. I am currently using offline compilation for my GLSL (for Vulkan) and MSL (for Metal) shaders. What are your workflows for situations like this? For those using tools like SPIR-V Cross and shaderc, what has your experience been with these tools keeping up to date with the latest features in the specs?
-
How are Vulkan, CUDA, Triton and all other things connected?
For cross-platform support look at WebGPU and Vulkan (e.g,: [0] [1]. Essentially, you would need to write the func in WGSL or GLSL, HLSL or MSL. Each of these can be cross-compiled to SPIR-V (what Vulkan needs) with cross-compilers such as spirv-cross and naga.
-
Is it possible to get set number from uniform block reflection in glslang?
Just for reference, the library I'm using (both for compiling the shaders and for reflection), is SPIRV-Cross by the Khronos Group and here you have the docs for the reflection API. I wanted to check out `glslang` but honestly this one so far has worked like a charm.
-
Reflection on shaders to determine uniforms, samplers, attributes, etc.
Aside from SPIRV-Reflect, if you're using SPIRV-cross to cross compile your shaders, there is also a --reflect arg you can pass which spits out reflection info in JSON format. We already need to cross compile from spirv, so it just removes a tool in the chain to depend on.
- Finally managed to make my own shading language working! (need some opinion about the lang)
-
Need a little help with shaders.
For your own engine, use the format your API uses. If you need crossplatformness, there is a new path available. Write your shaders in a language that compiles to SPIR-V (HLSL/GLSL are the most obvious languages), and then use SPIR-V Cross to compile the SPIR-V back to HLSL/GLSL for other API to consume.
- Getting descriptors from SPIRV
ssgl
-
[2023 Day 8 (Part 2)] [Dart] Is it normal that the code takes ages to run?
It's here. I made a post about it too, there's some details in the comments on how this works.
-
[2023 Day 5 (Part 2)] [GLSL] If brute force doesn't work, you aren't using enough
Here I'm doing GLSL and running it via OpenGL on top of my own helper library (the main branch of the code repo explains it pretty well). For me it's the easiest way to code for a GPU by a wide margin, but I guess that's to be expected. For performance, the most important things here are using shared memory and persistent threads so there are less global reads and especially atomics (I wanted to do a local reduction on the end result but for whatever reason subgroup operations don't work on 64-bit integers and I didn't bother to write it out with shared memory)
-
Why there aren't graphics APIs designed to be source compatible with the CPU side like CUDA?
Some of it is fine-grained control, some is how itβs nice to be able to treat shaders as separate entities, some is just different preference. But no actual limitation, in fact I built a thing for that on top of OpenGL.
-
Why aren't there constantly more shading languages popping up all the time like other languages?
Include is probably your best bet there. Personally I use this system that I made, which borrows the single source programming model from CUDA so that shaders are just reinterpreted C++ code that can sit within the rest of the program. This means I can call the same functions from C++ and the shaders, and includes work just like any other includes.
-
What are the best C++ talks that one should watch?
I also already have a library that gives compile time errors, by having the shaders just be a part of the C++ program :) This would also benefit slightly from having embedded files, as I wouldn't need to do the runtime hacks that are currently in place.
-
Automatically selecting fragment shaders in a pipeline DSL based on vertex shader and bound samplers - good or bad idea?
As a side note, you may be interested in this library that someone posted on /r/GraphicsProgramming awhile ago. Haven't used it, but it seems like it might fit in with your general design philosophy.
-
True story right now
Because mine is the most faithful reproduction of GLSL I've seen. Almost all features work the same in C++ as they do in shaders -- the notable difference is that you can't pass swizzles by reference, and inout arguments have to be defined with a slightly wonky syntax.
-
Low-level OpenGL abstractions
The culmination of my attempts at wrapping OpenGL is ssgl, which foregoes basically all binding and lets you write shaders along C++ with semi-automatic lambda capture. The underlying implementation is filled with dragons, but from personal experience it's just bonkers how much nicer it is to work with compared to any other approach I've used.
-
A simple way to enforce (standard) header include order?
I have a library that due to its nature (it defines a domain-specific language within C++) has to define macros for a bunch of words that some standard headers use as variable names. This causes the standard headers to completely break if my library headers are included before them, and the errors are less than intuitive. Is there a simple way to produce a meaningful error (like "library header must be included last") if a standard header is included after the library headers? Googling didn't help much, and at a quick glance standard headers don't appear to contain too many extremely common names that I could #define to static_assert or something. I'm fine with the sensible error being limited to a few of the big standard implementations, so the option of just going through the headers and finding enough such names is doable, but it'd be nice to have a cleaner solution.
-
Learning OpenGL
Yeah, the state machine aspect does make debugging cumbersome, and it's very easy to forget some option in the wrong setting. But I don't fully agree with "a collection of spells", I think the steps to achieve something are (mostly) pretty straight forward. Though maybe memories go sweeter with time, I haven't written any binding code after making ssgl :-)
What are some alternatives?
rust-gpu - π Making Rust a first-class language and ecosystem for GPU shaders π§
slang - Making it easier to work with shaders
naga - Universal shader translation in Rust
Wisdom-Shaders - A Minecraft shaderspack. Offers high performance with high quality at the same time.
glslang - Khronos-reference front end for GLSL/ESSL, partial front end for HLSL, and a SPIR-V generator.
SDL_shader_tools - Shader compiler and tools for SDLSL (Simple Directmedia Layer Shader Language)
SPIRV-Reflect - SPIRV-Reflect is a lightweight library that provides a C/C++ reflection API for SPIR-V shader bytecode in Vulkan applications.
SHADERed - Lightweight, cross-platform & full-featured shader IDE
shaderc - A collection of tools, libraries, and tests for Vulkan shader compilation.
Fwog - Froggy OpenGL Engoodener
rivi-loader - Vulkan Compute program loader in Rust
glbinding - A C++ binding for the OpenGL API, generated using the gl.xml specification.