3 ms·
One issue is you need rocm 7 which only just came out. Another is that people unsportingly write things in cuda. It'll be a "just works" thing eventually, eve
by JonChesterfield 1y ago
One issue is you need rocm 7 which only just came out.
Another is that people unsportingly write things in cuda.
It'll be a "just works" thing eventually, even if you need software from outside AMD to get it running well.
- rbanffy 1y ago> Another is that people unsportingly write things in cuda. Whether we like it or not, CUDA is the de-facto standard for these things. I wonder how much effort would it take for a company the size of AMD to dedicate a couple million dollars a year to track CUDA as closely as feasible. A couple million dollars is a rounding error for a leading silicon maker.
- JonChesterfield 1y agoPersonally I love it but then I'm also working on a cuda to amdgpu compiler. I'm probably the only person doing that with a strix halo on his desk, should be debugging cuda on it shortly.
- rbanffy 1y agoThis is great news. We need more portable code and, with that, more competition. A single vendor world is boring.
- wmf 1y agoIt's called HIP.
- FuriouslyAdrift 1y agoThere and AMD-sponsored open source CUDA to ROCm transpiler out there (HIPIFY) https://github.com/ROCm/HIPIFY https://github.com/ROCm/HIPIFY
- JonChesterfield 1y agoYeah. Spectral's CTO is still the #2 contributor to that, https://github.com/ROCm/HIPIFY/graphs/contributors https://github.com/ROCm/HIPIFY/graphs/contributors. They tried really hard to make hipify work before accepting that forking clang was necessary. I thought I had an issue raised about hipify needing cuda's own headers to run but I can't find it now.