TileLang https://github.com/tile-ai/tilelang and stuff like Tile Kernels https://github.com/deepseek-ai/TileKernels will make CUDA obsolete one day.
CUDA-oxide: Nvidia's official Rust to CUDA compiler
71–80 of 132 posts
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#72Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#73Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#74Earlier quoted context omitted.
In AI-focused fields like business analytics and data science, yeah.
The 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.
Also Linux support for CUDA on laptops, especially with dual GPU setup isn't particularly great.
Most workstation class laptops are Windows based.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#75I wonder what it means for Slang[0]. Presumably the point is that people want to do GPU programming with a more modern language. But now you can just use Rust... (Disclaimer: I like Slang a lot.) [0]: https://shader-slang.org/
Also shading languages are more user friendly given their features.
Finally NVida already has Slang in production and those folks aren't going to rewrite shader pipelines into Rust.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#76> (em dash) no DSLs, no foreign language bindings, just Rust. Official CUDA port and they couldn't even bother with the introductory paragraph. Okay, I'll try to ignore it and read the docs. Hey a custom IR, this sounds interesti- > MLIR’s implementation, however, is C++ with a side of TableGen, a build system that requires you to compile all of LLVM, and debugging sessions that make you question your career choices.…
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#77TileLang https://github.com/tile-ai/tilelang and stuff like Tile Kernels https://github.com/deepseek-ai/TileKernels will make CUDA obsolete one day.
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#78This 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 stil…
My 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%2Fs...
Otherwise it isn't 1:1 with CUDA, and I am not counting everything else on CUDA ecosystem
Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#79Re: CUDA-oxide: Nvidia's official Rust to CUDA compiler
#80> (em dash) no DSLs, no foreign language bindings, just Rust. Official CUDA port and they couldn't even bother with the introductory paragraph. Okay, I'll try to ignore it and read the docs. Hey a custom IR, this sounds interesti- > MLIR’s implementation, however, is C++ with a side of TableGen, a build system that requires you to compile all of LLVM, and debugging sessions that make you question your career choices.…
What exactly are you upset about? Someone observing that MLIR is extremely complex and dependent on LLVM...?