4 ms·
> Unless AMD can provide a toolchain which takes cuda code and generates whatever it takes to run it with performance parity to Nvidia cards, it'll never take o
by dekken_ 7y ago
> Unless AMD can provide a toolchain which takes cuda code and generates whatever it takes to run it with performance parity to Nvidia cards, it'll never take off.
They have this. It's called HIP.
- missosoup 7y agohttps://rocm-documentation.readthedocs.io/en/latest/Programming_Guides/HIP-porting-guide.html https://rocm-documentation.readthedocs.io/en/latest/Programm... "HIP is designed to ease the porting of existing CUDA code into the HIP environment." Not even close an drop-in swappable alternative.
- tonypace 7y agoOf course not, and some things would never be ported. But if they had a massive cost advantage for a year or two in data centers, a lot of things would get ported, quickly.
- deleted 7y ago[deleted]
- pjmlp 7y agoDoes HIP support all the programming languages that are able to target CUDA, like Julia, Numba, .NET, Java, Haskell, Fortran, C++? Khronos did a big mistake to keep pushing C as the only compute language for so long, and it remains to be seen how much adoption SPIR-V is able to actually take from PTX. So unless HIP actually matches PTX, it is a non-starter.
- xiphias2 7y agoIn theory HIP is a modified LLVM, but as far as I know Julia uses a modified LLVM as well, so unless they are upstreamed, we can't use them together :( I guess I'm staying with NVIDIA with developer laptops for a long time, and maybe using AMD for ultrabook.
- pjmlp 7y agoExcept that some of the languages that target CUDA do so via PTX, not by migrating their compiler backends into LLVM. So if HIP will only work with LLVM, that is also a non-starter.