@@ -27,7 +27,7 @@ We've now accomplished these goals and stabilized the project.
27
27
28
28
### Updated to a newer Rust toolchain
29
29
30
- Rust- CUDA is a collection of crates, one of which is
30
+ Rust CUDA is a collection of crates, one of which is
31
31
[`rustc_codegen_nvvm`](https://github.com/Rust-GPU/Rust-CUDA/tree/main/crates/rustc_codegen_nvvm).
32
32
This crate plugs directly into the Rust compiler to generate [NVVM
33
33
IR](https://docs.nvidia.com/cuda/nvvm-ir-spec/index.html), which NVIDIA's tools then
@@ -36,10 +36,10 @@ allows your Rust code to call existing CUDA libraries (anything compiled into
36
36
[PTX](https://docs.nvidia.com/cuda/parallel-thread-execution)).
37
37
38
38
Because `rustc_codegen_nvvm` relies heavily on the Rust compiler's internals, it needs
39
- to exactly match with a particular compiler version. Up until recently, Rust- CUDA was
39
+ to exactly match with a particular compiler version. Up until recently, Rust CUDA was
40
40
stuck on a very old nightly version—`nightly-2021-12-04`. That is **over 3 years old**!
41
41
42
- Huge shoutout to new contributor <Gh user = " jorge-ortega" /> for [ bringing Rust- CUDA
42
+ Huge shoutout to new contributor <Gh user = " jorge-ortega" /> for [ bringing Rust CUDA
43
43
forward to ` nightly-2025-03-02 ` ] ( https://github.com/Rust-GPU/Rust-CUDA/pull/155 ) . With
44
44
this update, we've got much better compatibility with the Rust crate ecosystem and
45
45
access to new language features.
@@ -50,11 +50,11 @@ Jorge used a [draft PR](https://github.com/Rust-GPU/Rust-CUDA/pull/98) put toget
50
50
51
51
The [ latest NVIDIA CUDA toolkit is
52
52
` 12.x ` ] ( https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html ) . When
53
- Rust- CUDA was last maintained only ` 11.x ` was available. Rust- CUDA crates would error if
53
+ Rust CUDA was last maintained only ` 11.x ` was available. Rust CUDA crates would error if
54
54
CUDA was less than version ` 11.x ` , but the check also errored on ` 12.x ` . Supporting CUDA
55
55
` 12.x ` is critical as most users install the latest CUDA toolkit.
56
56
57
- <Gh user = " jorge-ortega" /> tested Rust- CUDA with CUDA ` 12.x ` successfully, giving
57
+ <Gh user = " jorge-ortega" /> tested Rust CUDA with CUDA ` 12.x ` successfully, giving
58
58
us confidence to enable initial support. New contributor <Gh user = " Schmiedium" /> then
59
59
[ updated the version check] ( https://github.com/Rust-GPU/Rust-CUDA/pull/165 ) , and
60
60
maintainer <Gh user = " LegNeato" /> integrated ` 12.x ` [ into CI] ( https://github.com/Rust-GPU/Rust-CUDA/pull/168 ) .
@@ -65,7 +65,7 @@ encountered!
65
65
66
66
### Fixed CI
67
67
68
- Rust- CUDA's CI was broken after three years of inactivity and there was significant
68
+ Rust CUDA's CI was broken after three years of inactivity and there was significant
69
69
technical debt.
70
70
71
71
As CI is critically important to quality, we focused on fixing and modernizing it. <Gh
@@ -75,7 +75,7 @@ addressed linker errors across both Windows and Linux. The [first passing CI
75
75
run] ( https://github.com/Rust-GPU/Rust-CUDA/actions/runs/13913964011/ ) was a huge
76
76
accomplishment and a culmination of a lot of debugging and development work.
77
77
78
- The Rust- CUDA project currently can't run GPU tests on GitHub Actions due to the lack of
78
+ The Rust CUDA project currently can't run GPU tests on GitHub Actions due to the lack of
79
79
NVIDIA GPUs. ** If you want to sponsor some CI machines, get in touch!**
80
80
81
81
Even without GPU tests, CI now provides a critical safety net for future development.
@@ -86,7 +86,7 @@ We merged over 16 outstanding pull requests from over 12 contributors as far bac
86
86
87
87
- [ #105 ] ( https://github.com/rust-gpu/rust-gpu/pull/105 ) by <Gh user = " DoeringChristian"
88
88
/>: Fixed a double-free caused by incorrect casting, significantly improving memory
89
- safety. While Rust- CUDA is written in Rust, we interface with CUDA libraries and tools
89
+ safety. While Rust CUDA is written in Rust, we interface with CUDA libraries and tools
90
90
written in C/C++ so issues like this can happen.
91
91
- [ #64 ] ( https://github.com/rust-gpu/rust-gpu/pull/64 ) by <Gh user = " kjetilkjeka" /> (the
92
92
` rustc ` ptx backend maintainer): Added pitched memory allocation and 2D memcpy
@@ -118,7 +118,7 @@ Thank you to all of our new contributors!
118
118
119
119
#### Cleaned up the project
120
120
121
- Rust- CUDA maintainer <Gh user = " LegNeato" /> went through the project and closed most of the
121
+ Rust CUDA maintainer <Gh user = " LegNeato" /> went through the project and closed most of the
122
122
outdated issues and any pull requests that were no longer relevant. Little things like
123
123
tags on GitHub were added to aid discoverablility.
124
124
@@ -140,7 +140,7 @@ we are thinking:
140
140
infrastructure to reduce duplication.
141
141
142
142
Of course, what's next will largely depend on who shows up and what they want to do!
143
- Rust- CUDA is 100% community-driven; none of us are paid to work on it.
143
+ Rust CUDA is 100% community-driven; none of us are paid to work on it.
144
144
145
145
## Relation to other GPU projects in the Rust ecosystem
146
146
@@ -171,8 +171,8 @@ unification with related projects:
171
171
abstraction for CUDA programming in Rust. We aim to explore how ` rust-cuda ` can
172
172
interoperate with ` cudarc ` or consolidate efforts.
173
173
174
- After digging deeper into the Rust- CUDA codebase, we're even more convinced these
175
- opportunities are real. The path to merging Rust- CUDA and Rust- GPU, in particular, looks
174
+ After digging deeper into the Rust CUDA codebase, we're even more convinced these
175
+ opportunities are real. The path to merging Rust CUDA and Rust GPU, in particular, looks
176
176
shorter and more relevant than we originally expected.
177
177
178
178
For a broader look at Rust and GPUs, check out the [ ecosystem overview
0 commit comments