> Is ZLUDA a drop-in replacement for CUDA?
> Yes, but certain applications use CUDA in ways which make it incompatible with ZLUDA
> What is the status of the project?
> This project is a Proof of Concept. About the only thing that works currently is Geekbench. It's amazingly buggy and incomplete. You should not rely on it for anything serious
It is a cool proof of concept but we don’t know how far away it is from becoming something that a company would willingly endorse. And I suspect AMD or Intel wouldn’t want to put a ton of effort into… helping people continue to write code in their competitor’s ecosystem.
https://www.jwz.org/blog/2012/06/i-have-ported-xscreensaver-...
https://dereferer.me/?https%3A//www.jwz.org/blog/2012/06/i-h...
Went there a few days ago. Got a colonoscopy picture. Even without deferrer/referrer.
However, they have gone around that by creating HIP which is a CUDA adjacent language that runs on AMD and also translates to CUDA for Nvidia GPUs. There is also the HIPify tool to automatically convert existing sources from CUDA to HIP. https://docs.amd.com/bundle/HIP-Programming-Guide-v5.3/page/...
You can guess how much money lawyers have been paid over that circumstance.
And FWIW, that seems to be a reasonable result given the overall market structure at the moment. Having all eggs in the Nvidia basket is great for Nvidia shareholders, but not for customers and probably not even for the health of the surrounding industry.
Let's suppose that an open-source CUDA API is in a legal gray zone that could only be clarified by a judge.
Could a company like AMD create a wholly owned subsisiary to make an attempt, whithout exposing the parent company to legal liability?
Furthermore, CUDA is a language (dialect of C/C++) not an API, so that precedent may not have much weight.
I'm reasonably sure they could reimplement CUDA from a copyright / trademark perspective. It's possible that they could be blocked with patents though.
IIRC, the verbatim copying of rangeCheck didn't make it to SCOTUS. They really did instead rule on the copyrightability of the "structure, sequence, and organization" of the Java API as a whole.
A more aggressive approach was tried during the Xbox 360 era with the Games For Windows Live framework and by removing their games from the Steam store. It ended up catastrophically bad and they had to backtrack on both decisions.
The irony of Proton de facto killing any chance for native linux ports of windows games isn't lost to them, either.
Playing games on linux is not a threat to microsoft. The money they loose on that is miniscule.