HIPIFY

Yeah. Spectral's CTO is still the #2 contributor to that, 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.

There and AMD-sponsored open source CUDA to ROCm transpiler out there (HIPIFY) https://github.com/ROCm/HIPIFY

https://docs.scale-lang.com/ https://github.com/ROCm/HIPIFY

AMD has hipify for this, which converts cuda code to hip. https://github.com/ROCm/HIPIFY

Have you looked at ZLUDA? Edit: Or HIPIFY, a tool made by AMD as a translation for CUDA. https://github.com/ROCm/HIPIFY/blob/amd-staging/README.md

I would love for someone to run HIPIFY[0] on this and prove that it works (or doesn't). I'd do it myself, but I am unable to at this time. [0] https://github.com/ROCm-Developer-Tools/HIPIFY

> AMD needs to be funding a CUDA shim that allows people to port stuff directly to their cards. And they need to NOT be segmenting the consumer and professional cards software ecosystems. Isn't that what HIPIFY does? https://github.com/ROCm/HIPIFY

Does HIPIFY not meet your standards? https://github.com/ROCm/HIPIFY

I would start to look into using ROCm/HIP to port the code. Some of it can be done automatically and some will need customizations [0]. Then, you rent time on my systems and see what the performance is. If it is good, you rent more, for longer to bring the pricing down. Effectively, we are taking the capex/opex risk off your shoulders. The key point here is that we have actual availability and we aren't just reselling someone else's hardware. Dual 9754's are indeed quite nice. ;-) [0] https://github.com/ROCm/HIPIFY

> what would be the point for someone to add ROCm support to various pieces of software which currently require CUDA It isn't just old cards though, CUDA is a point of centralization on a single provider during a time when access to that providers higher end cards isn't even available and that is causing people to look elsewhere. ROCm supports CUDA through the included HIP projects... https://github.com/ROCm/HIP https://github.com/ROCm/HIPCC https://github.com/ROCm/HIPIFY The later will regex replace your CUDA methods with HIP methods. If it is as easy as running hipify on your codebase (or just coding to HIP apis), it certainly makes sense to do so.

That's what https://github.com/ROCm/HIPIFY is (as a part of ROCm)

> CUDA can be translated to HIP using automated tools. Not just automated, but also open source. https://github.com/ROCm-Developer-Tools/HIPIFY

> AMD had a system which had a tool to do conversion a while back but I recall them not supporting it seriously. They are supporting it seriously now. It is being actively developed and improved. https://github.com/ROCm-Developer-Tools/HIPIFY

This is what they are referring to: https://github.com/ROCm-Developer-Tools/HIPIFY