Expand description
sys — thin Rust wrappers over cudarc’s raw *::sys FFI for
library entry points that aren’t yet exposed by the safe layer.
Each sub-module is feature-gated to match its cudarc parent so the crate still builds with the corresponding library disabled.
Modules§
- cublas
- Sys-level safe wrappers for the cuBLAS entry points cudarc 0.19 doesn’t expose through its safe layer.
- cublaslt
- Thin local wrappers over
cudarc::cublaslt::sysfor the entry points cudarc 0.19.4’s safe layer doesn’t expose. Each helper isunsafe fnif it dereferences raw handles; the safe shape is just “create / set-attribute / destroy” RAII over the opaque handle. - cuda_
driver - Thin, panic-safe wrappers around CUDA driver-API entry points
that cudarc 0.19 only exposes at the
syslevel. - cudnn
- Thin Rust safety layer over the cuDNN v9 backend graph FFI.
- cufft
- Local FFI bindings for cuFFT entry points cudarc 0.19.4 doesn’t expose.
- curand
- Thin Rust-level wrappers over [
cudarc::curand::sys] for the cuRAND host-API entry points that aren’t surfaced by the safe [cudarc::curand::CudaRng] handle: - cusolver
- Crate-private FFI thunks around
cudarc::cusolver::sys. - cusparse
- Thin safe-ish wrappers over
cudarc::cusparse::sysentry points Phase 4 needs but the safe layer doesn’t provide. - cutensor
- Local sys-level wrappers around
cudarc::cutensor::sysfor the cuTENSOR entry points the safecudarc::cutensor::resultmodule does not expose (Reduce/ElementwiseBinary/ElementwiseTrinary create+execute, Permutation create+execute, predefined compute descriptors).