Skip to content

Commit 12824a2

Browse files
committed
Avoid Rust-CUDA in documentation/comments.
By using `Rust CUDA` instead.
1 parent 5281459 commit 12824a2

File tree

6 files changed

+7
-7
lines changed

6 files changed

+7
-7
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Other projects related to using Rust on the GPU:
9292
cargo build
9393
```
9494

95-
## Use Rust-CUDA in Container Environments
95+
## Use Rust CUDA in Container Environments
9696

9797
The distribution related Dockerfile are located in `container` folder.
9898
Taking ubuntu 24.04 as an example, run the following command in repository root:

crates/rustc_codegen_nvvm/src/builder.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@ macro_rules! math_builder_methods {
213213
_ => {
214214
self.cx.fatal(format!(
215215
"Unimplemented 128-bit integer operation '{}' with {} arguments. \
216-
This operation is not yet supported in Rust-CUDA. \
216+
This operation is not yet supported in Rust CUDA. \
217217
Consider using 64-bit integers or filing an issue at \
218218
https://github.com/Rust-GPU/Rust-CUDA/issues",
219219
stringify!($name),

examples/cuda/gemm/src/main.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
//! Example demonstrating GEMM (General Matrix Multiply) on CUDA using Rust-CUDA.
1+
//! Example demonstrating GEMM (General Matrix Multiply) on CUDA using Rust CUDA.
22
//!
33
//! This example benchmarks naive and tiled GEMM kernels as well as cuBLAS for various matrix sizes.
44
//! It uses the `cust` crate for CUDA management and `ndarray` for host-side matrix operations.

guide/src/guide/getting_started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -234,7 +234,7 @@ components = ["rust-src", "rustc-dev", "llvm-tools-preview"]
234234

235235
There is also a [Dockerfile](Dockerfile) prepared as a quickstart with all the necessary libraries for base cuda development.
236236

237-
You can use it as follows (assuming your clone of Rust-CUDA is at the absolute path `RUST_CUDA`):
237+
You can use it as follows (assuming your clone of Rust CUDA is at the absolute path `RUST_CUDA`):
238238

239239
- Ensure you have Docker setup to [use gpus](https://docs.docker.com/config/containers/resource_constraints/#gpu)
240240
- Build `docker build -t rust-cuda $RUST_CUDA`

tests/compiletests/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# Compiletests for Rust-CUDA
1+
# Compiletests for Rust CUDA
22

3-
This directory contains compile tests for the Rust-CUDA project using the `compiletest` framework.
3+
This directory contains compile tests for the Rust CUDA project using the `compiletest` framework.
44

55
The code in these tests is not executed. Tests check that the compiler compiles
66
correctly. Tests in `dis/` verify correct PTX output.

tests/compiletests/src/main.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ fn main() {
6565

6666
// HACK(eddyb) force `compiletest` to pass `ui/...` relative paths to `rustc`,
6767
// which should always end up being the same regardless of the path that the
68-
// Rust-CUDA repo is checked out at (among other things, this avoids hardcoded
68+
// Rust CUDA repo is checked out at (among other things, this avoids hardcoded
6969
// `compiletest` limits being hit by e.g. users with slightly longer paths).
7070
std::env::set_current_dir(tests_dir).unwrap();
7171
let tests_dir = PathBuf::from("");

0 commit comments

Comments
 (0)