News for hackers. Stuff that matters.
Re:Cuda.jl v3.3: union types, debug info, graph APIs by jpsamaroo on Monday June 14, 2021 @07:59AM (#27501552)
AMD has done great work in a very short amount of time, but let's not forget that they're still very new to the GPU compute game. The ROCm stack is overall still pretty buggy, and definitely hard to build in ways other than what AMD deems officially supported.

As AMDGPU.jl's maintainer, I do certainly appreciate more users using AMDGPU.jl if they have the ability to, but I don't want people to think that it's anywhere close in terms of maturity, overall performance, and feature-richness compared to CUDA.jl. If you already have access to an NVIDIA GPU, it's painless to setup and should work really well for basically anything you want to with it. I can't say the same about AMDGPU.jl right now (although we are definitely getting there).

Re:Cuda.jl v3.3: union types, debug info, graph APIs by zamalek on Monday June 14, 2021 @11:53AM (#27504111)
Genuine question: why can't Vulkan Compute be used instead of CUDA and ROCm?

Julia has all the tools required to "magically" transform code into SPIR-V kernels. Couldn't `:()` syntax be used to create kernels?

Re:Cuda.jl v3.3: union types, debug info, graph APIs by eigenspace on Monday June 14, 2021 @12:29PM (#27504624)
Re:Cuda.jl v3.3: union types, debug info, graph APIs by snicker7 on Tuesday June 15, 2021 @10:40AM (#27516181)
oneApi.jl has a Julia to SPIR-V (Vulkan) compiler.