ptillet
commented
3 years ago I have thought about it. At some point in the not-so-distant past I had an AMD backend working through the AMDGPU LLVM target and the OpenCL runtime. It would be a fairly low amount of work to bring this back to life, though it would be preferrable to replace OpenCL by HIP.
I am working full-time on Triton at OpenAI, and mostly focused on A100 at the moment. That said, I would be down to spend some time reviving AMD support in the Triton compiler (though it would not support newer matrix instructions) if someone was willing to help with runtime support -- that is, updating https://github.com/ptillet/triton/tree/master/lib/driver to have hip{buffer,module,device,etc} classes that parallel cu{buffer,module,device,etc.}. Happy to chat more about it if this is something AMD is willing to help with :)
jithunnair-amd
gururise
jeffdaily
Do you plan to add support for a HIP backend in addition to the CUDA backend? HIP is a C++ Runtime API and Kernel Language that allows developers to create portable applications for AMD and NVIDIA GPUs from single source code.
Adding support for the HIP backend would enable the triton library to also support AMD GPUs. The HIP API very closely resembles the CUDA API, and we have tools such as hipify to allow us to easily "translate" most of the CUDA sources into HIP sources.