4 ms·
This is a bit good for Rust if you want to use the language with CUDA. The problem is, it still doesn't really move the needle if you really don't like running
by rvz 6mo ago
This is a bit good for Rust if you want to use the language with CUDA. The problem is, it still doesn't really move the needle if you really don't like running closed source drivers and runtime binaries and care about open source.
Continuing from this discussion [0], this only makes it a Rust or a CUDA problem rather than a Python, CUDA and a PyTorch one if there bug in one of them.
Yet at the end of the day, it still uses Nvidia's closed source CUDA compiler 'nvcc' which they will never open source. A least Mojo promises to open source their own compiler which compiles to different accelerators with multiple backend support.
Unlike this...but uses Rust.
[0] https://news.ycombinator.com/item?id=48067228 https://news.ycombinator.com/item?id=48067228
- bigyabai 6mo ago> it still doesn't really move the needle if you really don't like running closed source drivers and runtime binaries Those people probably did not buy an Nvidia GPU for themselves. It should be common knowledge that the "Open" Nvidia drivers still run gigantic firmware blobs to dispatch complex workloads. And Nouveau is close to useless for GPGPU compute.
- pjmlp 6mo agoMojo remains to be seen if it isn't another Swift for Tensorflow, apparently 1.0 won't even support Windows properly.
- semiinfinitely 6mo ago[flagged]
- bigyabai 6mo agoThe majority of computer owners on planet Earth
- OtomotO 6mo agoBut also the majority of programmers?
- bigyabai 6mo agoIn AI-focused fields like business analytics and data science, yeah.
- vlovich123 6mo agoThe claim is that people are running CUDA on Windows for business analytics and data science? This feels less likely an accurate picture and more likely any mass data processing is already happening on Linux K8s clusters.
- pjmlp 6mo agoYes, if they happen to run tooling like Excel, PowerBI, Tableau,.... Also Linux support for CUDA on laptops, especially with dual GPU setup isn't particularly great. Most workstation class laptops are Windows based.
- vlovich123 6mo agoAFAIK neither excel nor Tableau has any CUDA functionality to begin with so I’m not sure what point you’re trying to make. No one is doing CUDA number crunching on local laptops - either the problem is big enough to warrant a proper data center or it’s small enough that a local CPU is fine. Local CUDA is a weird middle ground that requires a lot of complexity for marginal compute capability. Linux support for CUDA in such an environment is irrelevant.
- pjmlp 6mo agoBecause you are lost how a day in the office of a big corporation looks like. Also this attitude about people not doing compute on laptops, is yet another reason why Intel and AMD keep losing to NVidia.
- beanjuiceII 6mo agomany people
- fhn 6mo agoyou mom!
- deleted 6mo ago[deleted]
- deleted 6mo ago[deleted]
- pjmlp 6mo agoAll the game devs that forced Valve to come up Proton for Steam Deck to have any content.
- the__alchemist 6mo agoIMO this has nothing to do with open source as an ideology; just a practical (and official?) lib for adding GPU interaction to your rust programs.
- zamalek 6mo agoMy sentiment matches your exactly. I'm sick and tired of CUDA - but it's really not going to change. Could maybe be forked with some dynamic smarts, HIP is basically 1:1 with CUDA: https://github.com/amd/amd-lab-notes/blob/release/hipify%2Fsrc%2Fgpu_macros.h https://github.com/amd/amd-lab-notes/blob/release/hipify%2Fs...
- pjmlp 6mo agoDoes it support a graphical GPU debugging for C++, Fortran and Python JIT GPU code? Otherwise it isn't 1:1 with CUDA, and I am not counting everything else on CUDA ecosystem
- zamalek 6mo agoDebugging (gdb, but GUI frontends exist for gdb in general): https://rocm.docs.amd.com/projects/HIP/en/latest/how-to/debugging.html https://rocm.docs.amd.com/projects/HIP/en/latest/how-to/debu... Fortran: https://github.com/ROCm/hipfort https://github.com/ROCm/hipfort Python (not sure about JIT): https://rocm.docs.amd.com/projects/hip-python/en/latest/ https://rocm.docs.amd.com/projects/hip-python/en/latest/
- pjmlp 6mo agoAll those are far from the 1:1 CUDA experience.
- charcircuit 6mo agoConsidering how fast everything is changing with GPUs and how competitive it is. It doesn't make sense to have an open source driver.
- nihalpasham 6mo agoSmall 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 code still goes through normal rustc/LLVM codegen. You still need the NVIDIA driver/toolkit pieces to run CUDA code and load PTX on NVIDIA GPUs, so this does not change the broader CUDA ecosystem/dependency story. But it is not “Rust source handed to nvcc”; it is a Rust compiler backend generating device code.