5 ms·
What is the relation between this and Zluda[1]? [1]https://github.com/vosen/ZLUDA https://github.com/vosen/ZLUDA
by Ygg2 1y ago
What is the relation between this and Zluda[1]?
[1]https://github.com/vosen/ZLUDA https://github.com/vosen/ZLUDA
- krapht 1y agoHIP is something you can put in production and Zluda is a proof-of-concept?
- Ygg2 1y agoOk, but it's that their only difference? Zluda was supported by AMD for some time. Is it just that Hip is currently more complete?
- 3836293648 1y agoYou using HIP was supported by AMD. Zluda was getting support from AMD. Not the same kind of support
- Ygg2 1y agoYeah, I get it now. HIP converts CUDA code to HIP code, then converts that code to ROCm (AMD) or PTX(nVidia). Zluda converts CUDA code to PTX, but that CUDA license was changed during 2021 to prevent these kinds of efforts. This is why AMD dropped all involvements with Zluda (they were contributing code to it).
- almostgotcaught 1y agoLol that's like asking what's the difference between the empire state building and the shed in my backyard: one is the runtime that the company that owns/makes the GPUs has been building for 10 years and the other is a (good) solo project.
- Ygg2 1y agoWell, god forbid people ask questions.
- deleted 1y ago[deleted]
- spmurrayzzz 1y agoThere's no relation per se (apart from AMD once being involved, before asking the developer to take the project offline). It is worth noting however that they accomplish their goals very differently. ZLUDA is now DoA-ware because of nvidia's use constraint in their license regarding translation layers. HIP doesn't have this issue.
- TheCycoONE 1y agoSince no one answered you, HIP is a compile time target, you use hipify to transform your cuda code, then you compile it with hipcc, and hopefully everything works; or you target HIP directly. ZLUDA was a translation layer, ala wine for cuda applications.
- Ygg2 1y agoThanks a thousand times over.