rust-gpu icon indicating copy to clipboard operation
rust-gpu copied to clipboard

🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧

Results 149 rust-gpu issues
Sort by recently updated
recently updated
newest added

Let's start off with the simplest hlsl shader I can more or less come up with to do bindless support, which I would like to port to rust-gpu. Notice that...

mcp: accepted
a: ark

@bjorn3 mentioned in https://github.com/EmbarkStudios/rust-gpu/issues/134#issuecomment-716101846 that [Mesa's LLVMpipe](https://docs.mesa3d.org/drivers/llvmpipe.html) can be a possibility for headlessCI testing. Did some quick investigation and LLVMpipe has traditionally supported OpenGL but has recently merged in early...

t: help wanted
a: test

This is a design issue to research and figure out how to the bindings between shaders and our Rust CPU code (native or WASM) should look like. How should resources...

t: design

# Summary This proposal attempts to address #232, #180, and #8. StorageBuffers, aka Buffer Blocks, are the primary inputs / outputs to compute shaders, though they can also be used...

t: design
mcp: rfc needed

We want to have the same types of safety on the GPU as we do on the CPU. One of those areas that make it easy to introduce race conditions...

t: design

A few options here: - Hack the compiler to just output the data layout that we want - Add `#[repr(std140)]` and `#[repr(std430)]` to the language frontend (maybe have better names...

t: design

Check can be disabled by specifying `skip-toolchain-check` feature on either `rustc_codegen_spirv` or `spirv_builder`

# Summary `rustc_codegen_spirv` is compiled and discovered in a very hacky way. Cargo compiles `rustc_codegen_spirv` because it is inside `spirv-builder`'s Cargo.toml as a dependency, and then `spirv-builder` discovers the `rustc_codegen_spirv`'s...

t: enhancement

I was hoping to learn how to write rust-gpu shaders, so I was going through the tutorial, and have to run the CPU version on my old mac air. I...

t: enhancement

We've known for a while that the existing inliner+`mem2reg` setup can lead to long compile times (e.g. #851), but we've never had a simple stress test to measure that behavior...