nihalpasham

5 ms·

1. 1.▲
   by nihalpasham 4mo ago

   Small correction: cuda-oxide does not use `nvcc` to compile Rust kernels. The device path is roughly: rustc frontend/MIR -> cuda-oxide’s Pliron-based IR/lowering pipeline -> LLVM IR -> PTX via LLVM’s NVPTX backend. Host c
2. 2.▲
   by nihalpasham 4mo ago

   Yes, absolutely. That is one of the advantages of cuda-oxide being single-source Rust: the host and device code can refer to the same Rust types, and the compiler has enough information to make the device-side layout match what rustc chose
3. 3.▲
   by nihalpasham 4mo ago

   Hi, author of cuda-oxide here. Yes, I think that’s basically the right framing: cudarc and cuda-oxide sit at different points in the stack. cudarc is a host-side CUDA API for Rust: loading modules, managing contexts/streams/events