News for hackers. Stuff that matters.
Re:Lisa Su Saved AMD. Now She Wants Nvidia's AI Crown by kcb on Friday June 02, 2023 @09:12PM (#36172732)
> and you're drinking koolaid if you think its still relevant for greenfield projects.

So I want to start a new GPU compute project today. Obviously this will primarily be deployed to AWS/Azure/etc, which means only high-end GPUs available are Nvidia. What do you recommend developing this application with?

The way I see it, you would have to be drinking koolaid to use anything besides CUDA.

Re:Lisa Su Saved AMD. Now She Wants Nvidia's AI Crown by DiabloD3 on Friday June 02, 2023 @10:10PM (#36173018)
Why do you think I can't use standard APIs on Nvidia? I literally just said same compiler does both; Nvidia sits on the Khronos committee! They co-wrote the API that everyone uses, that their compiler also speaks!
Re:Lisa Su Saved AMD. Now She Wants Nvidia's AI Crown by Miraste on Friday June 02, 2023 @10:34PM (#36173163)
Vulkan Compute is not an alternative to CUDA. There's a reason PyTorch doesn't provide Vulkan in their official binaries. It's in the source, though--build it yourself, try running any recent ML project, and see what happens.
Re:Lisa Su Saved AMD. Now She Wants Nvidia's AI Crown by DiabloD3 on Wednesday June 07, 2023 @10:50PM (#36236567)
Thats a weird strawman; compute in Vulkan is a replacement compute in OpenGL and legacy D3D, and as a twin sibling to compute in D3D12.

OpenCL is the actual intended replacement for all the pre-standard APIs, and has achieved its goals. If you want SPIR-V IR, OpenCL allows this and all the major vendor impls support it.

CUDA has no equivalent for SPIR-V, and never will. Nvidia's own internal IR is not, and never will be, documented nor stable across driver versions. This is a massive downside for ML middlewares, as they have no way of directly emitting optimal code that cannot easily be represented in the HLSL-flavored syntax in CUDA.