ash
Rust-CUDA
ash | Rust-CUDA | |
---|---|---|
13 | 37 | |
1,708 | 2,894 | |
2.5% | 2.7% | |
8.5 | 0.0 | |
5 days ago | 6 months ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
ash
-
Going beyond build.rs: introducing cargo-px
If you want to automate the creation of certain code that will be nested under the src directory, and committed into source control, there are a variety of ways to do that. One option is to create a sub-crate in your project that does the code-gen and you can run it as needed. The ash project is an example of this.
-
Hey Rustaceans! Got a question? Ask here (16/2023)!
There is also [Vulkano](https://github.com/vulkano-rs/vulkano). It has a safe high level api and lower level layers, all the way down to [ash](https://github.com/ash-rs/ash) which is more or less raw vulkan. It's more explicit and verbose than [wgpu](https://github.com/gfx-rs/wgpu) though, so maybe try wgpu first and see how you like it.
-
A new picture of my ray tracing voxel engine (Vulkan/RTX/Rust)
Yes. I use Ash bindings for Vulkan and raw GLSL for shaders. I tried to use spirv-std for shaders—it was really great to have the benefits of Rust (structs, enums, strict type assertions, etc.)—until I needed to use buffer references. Unfortunaly, it is not yet implemented.
-
go-vk - A new Go language binding for Vulkan
This is great, of all the vulkan go bindings I have been waiting for one that uses vk.xml to generate the bindings, because it's the only viable way to keep the bindings up-to-date. (fyi the popular [ash-rs](https://github.com/ash-rs/ash) is created the same-way).
-
undefined symbol: wlEglCreateSurfaceExport
Hi, I am having an issue on pop-os wayland where when I run a vulkan application I get an error symbol lookup error: /lib/x86_64-linux-gnu/libnvidia-vulkan-producer.so: undefined symbol: wlEglCreateSurfaceExport I have tested this with https://github.com/ash-rs/ash running the triangle example.
-
State of GPGPU in 2022
Nice and simple. Its quite portable too. But simplicity and ease of use come with some limitations. Ash is much more complex but can extract every bit of power from your card if needed. Wgpu-rs github comes with many examples and you can find a really nice tutorial here
-
I made a video with every single debug render on a pathtracer I'm programming in Rust
low level vulkan bindings
-
How to render text with rust?
Glium and ash provide low level access to different common graphics api's. I'm sure there's a good directx-11/12 bindings as well but I'm unfamiliar with what people use.
-
https://np.reddit.com/r/rust/comments/pgruh2/most_efficient_way_to_write_and_read_large/hbfavpa/
fn read_uncompressed_buffer( reader: &mut R, length: usize, // estimated via a seek or other mechanism file_is_little_endian: bool, ) -> Result> { let bytes = length * std::mem::size_of::(); // it is undefined behavior to call read_exact on un-initialized, https://doc.rust-lang.org/std/io/trait.Read.html#tymethod.read // see also https://github.com/MaikKlein/ash/issues/354#issue-781730580 let mut buffer = vec![0u64, length]; unsafe { // transmute u64 to bytes. let slice = std::slice::from_raw_parts_mut( buffer.as_mut_ptr() as *mut u8, length * std::mem::size_of::(), ); reader.read_exact(slice)?; } if is_native_little_endian() != file_is_little_endian { swap(&mut buffer, file_is_little_endian) } }
-
Most efficient way to write and read large amounts of u64s?
// it is undefined behavior to call read_exact on un-initialized, https://doc.rust-lang.org/std/io/trait.Read.html#tymethod.read // see also https://github.com/MaikKlein/ash/issues/354#issue-781730580 let mut buffer = vec![0u64, length]; unsafe { // transmute u64 to bytes. let slice = std::slice::from_raw_parts_mut( buffer.as_mut_ptr() as *mut u8, length * std::mem::size_of::(), ); reader.read_exact(slice)?; } if is_native_little_endian() != file_is_little_endian { swap(&mut buffer, file_is_little_endian) }
Rust-CUDA
-
[Media] Anyone try writing a ray tracer with rust? It's pretty fun!
Source code [here](https://github.com/ihawn/RTracer) if anyone is interested in taking a look or giving feedback. As a side question, does anyone have any general advise on getting GPU compute working with rust? I tried [this project](https://github.com/Rust-GPU/Rust-CUDA) but had a bunch of issues (And it doesn't look like an active repo anyways)
-
Is rust or python better for Machine learning? Or is there enough decent frameworks?
You have this https://github.com/Rust-GPU/Rust-CUDA
-
toolchain nightly package building issue
What I'm trying to do is check out https://github.com/Rust-GPU/Rust-CUDA for a class project.
- [Rust] État de GPGPU en 2022
- Which crate for CUDA in Rust?
-
Announcing cudarc and fully GPU accelerated dfdx: ergonomic deep learning ENTIRELY in rust, now with CUDA support and tensors with mixed compile and runtime dimensions!
Be warned, NON_BLOCKING streams do not fully synchronize with sync host to device copies. They are not guaranteed to actually finish by the time they return. Meaning its possible to initiate a copy, then initiate a kernel launch, and have the copy be unfinished by the time the kernel is launched. This caused so many confusing bugs that i personally decided to stop using NON_BLOCKING altogether in rust-cuda. https://github.com/Rust-GPU/Rust-CUDA/issues/15
-
In which circumstances is C++ better than Rust?
- Cuda is not doing by FFI linking, instead is compiling CUDA code natively in Rust https://github.com/Rust-GPU/Rust-CUDA and even if it not complete as the C++ SDK is more than a toy
- I learned 7 programming languages so you don't have to
-
GNU Octave
Given your criteria, you might want to consider (modern) C++.
* Fast - in many cases faster than Rust, although the difference is inconsequential relative to Python-to-Rust improvement I guess.
* _Really_ utilize CUDA, OpenCL, Vulcan etc. Specifically, Rust GPU is limited in its supported features, see: https://github.com/Rust-GPU/Rust-CUDA/blob/master/guide/src/... ...
* Host-side use of CUDA is at least as nice, and probably nicer, than what you'll get with Rust. That is, provided you use my own Modern C++ wrappers for the CUDA APIs: https://github.com/eyalroz/cuda-api-wrappers/ :-) ... sorry for the shameless self-plug.
* ... which brings me to another point: Richer offering of libraries for various needs than Rust, for you to possibly utilize.
* Easier to share than Rust. A target system is less likely to have an appropriate version of Rust and the surrounding ecosystem.
There are downsides, of course, but I was just applying your criteria.
-
Your average rustafarians
Technically, yes. There are crates for OpenCL and CUDA, although official ROCm support does not exist yet.
What are some alternatives?
learn-wgpu - Guide for using gfx-rs's wgpu library.
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
wgpu-rs - Rust bindings to wgpu native library
wgpu - A cross-platform, safe, pure-Rust graphics API.
vulkan-tutorial-rust - Following the vulkan tutorial(https://vulkan-tutorial.com/) using the Rust programming language.
rust-ndarray - ndarray: an N-dimensional array with array views, multidimensional slicing, and efficient operations
rust-gpu-compute-example - Minimal example of using rust-gpu and wgpu to dispatch compute shaders written in rust.
CUDA.jl - CUDA programming in Julia.
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
GLSL - GLSL Shading Language Issue Tracker
vulkanalia - Vulkan bindings for Rust.
WeasyPrint - The awesome document factory