Our great sponsors
Orochi | naga | |
---|---|---|
5 | 28 | |
187 | 1,491 | |
12.8% | 0.7% | |
5.7 | 9.2 | |
4 days ago | 6 months ago | |
C++ | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
Orochi
-
Blender 3.6 (huge AMD gains with HIP RT) reaches Beta Phase 3
While you're waiting for the HIP SDK to release, check out Orochi as an alternative https://github.com/GPUOpen-LibrariesAndSDKs/Orochi
-
AMD Posts Patch Enabling Vega APU/GPU Support For Blender's HIP Backend
This isn't a full-fledged SDK but if you develop using the driver/runtime API and nvrtc on Linux, you could certainly use this library to make it run on Windows https://github.com/GPUOpen-LibrariesAndSDKs/Orochi Bonus - it also lets you compile a single binary that runs on both CUDA and HIP!
-
First time in 2 years I was able to get Blender running with an AMD GPU on Linux!
You can't run CUDA binaries directly. But you can use a wrapper library like Orochi to run both CUDA and HIP using a single binary that dynamically links with CUDA/HIP libraries at runtime https://github.com/GPUOpen-LibrariesAndSDKs/Orochi
-
How are Vulkan, CUDA, Triton and all other things connected?
I stumbled across orochi from AMD while looking for their FSR2.0 implementation, which basically boils down to being a wrapper over Cuda and HIP. I don't know if it is still maintained or functional, but heres the link if anyone is interested: https://github.com/GPUOpen-LibrariesAndSDKs/Orochi
- Orochi – dynamic loading of HIP/CUDA from a single binary
naga
- How does webgpu planning to use webgl shaders?
-
I want to talk about WebGPU
That wouldn't have been all that different from WGSL though, the most important thing is that whatever WebGPU uses for its shaders can be translated to and from SPRIV (and WGSL does that too (e.g. via https://dawn.googlesource.com/tint and https://github.com/gfx-rs/naga).
-
Survey: How have shader compilation messages been for you?
Hey all, wanted to put this link in here, where I'm proposing changing the API for errors in naga, so Naga can take ownership of error presentation and actually Make Shader Compilation Messages Comfy™: https://github.com/gfx-rs/naga/issues/2317
-
Start project on Metal, port to DX11?
EDIT: There is also naga but it does not take HLSL as input: https://github.com/gfx-rs/naga but you can use DirectXShaderCompiler to compile to SpirV, then use naga to compile to Metal.
-
Chrome ships WebGPU (available by default in Chrome 113)
And it seems that naga https://github.com/gfx-rs/naga Already has a working front/backend for wgsl.
-
Ray query example in Blade
This is basically Ray Tracing support in Blade. So far, only ray queries are supported. Unlike prior work on ray tracing in Rust, this is original due to all shader code being WGSL, see the Naga PR.
-
Does WGSL work well with vulkan?
There's a compiler that can translate from WGSL to SPIR-V called naga. Having such a compiler is essential, since WebGPU is planned to use WGSL and browsers are expected to implement rendering via Vulkan (and probably Metal and DX12).
-
Glsl transpiler, interpreter?
Not sure about on the CPU, but naga is a shading language transpiler you can write custom front/backends for.
-
Any guides/documentation on the WGSL shading language?
The spec docs are actually pretty useful https://www.w3.org/TR/WGSL/ besides that I was using naga's tests for reference https://github.com/gfx-rs/naga/tree/master/tests
-
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.
What are some alternatives?
SPIRV-Cross - SPIRV-Cross is a practical tool and library for performing reflection on SPIR-V and disassembling SPIR-V back to high level languages.
wgsl-cheat-sheet - Cheat sheet for WGSL syntax for developers coming from GLSL.
Stable-Diffusion-ONNX-FP16 - Example code and documentation on how to get Stable Diffusion running with ONNX FP16 models on DirectML. Can run accelerated on all DirectML supported cards including AMD and Intel.
shaderc - A collection of tools, libraries, and tests for Vulkan shader compilation.
kompute - General purpose GPU compute framework built on Vulkan to support 1000s of cross vendor graphics cards (AMD, Qualcomm, NVIDIA & friends). Blazing fast, mobile-enabled, asynchronous and optimized for advanced GPU data processing usecases. Backed by the Linux Foundation.
wgsl.vim - WGSL syntax highlight for vim
rocm-arch - A collection of Arch Linux PKGBUILDS for the ROCm platform
wgsl-mode - Emacs syntax highlighting for the WebGPU Shading Language (WGSL)
wgpu - Cross-platform, safe, pure-rust graphics api.
gpuweb - Where the GPU for the Web work happens!
rivi-loader - Vulkan Compute program loader in Rust
vscode-wgsl - VsCode Syntax highlight for WGSL files