-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build PoCL with Vulkan and CUDA as backends #278
Comments
It's probably fine to track that here. You can try and enable the build options in Yggdrasil, however, the problem is runtime dependency management. pocl_jll can't have to depend on CUDA_Runtime_jll (or the Intel/AMD equivalent) or it would be way to heavy to install. One option here is to split the built package into several JLLs, relying on pocl's loadable driver support, but that would probably require some changes in PoCL to support deferred driver loading (i.e. after Either way, I personally don't have the need / time for working on this. Feel free to take a stab, as long as it doesn't make the CPU use-case of PoCL significantly more complicated or large to install, I would be happy to have this feature. |
The Vulkan request was inspired by the existence of https://dawn.googlesource.com/tint and https://github.com/gfx-rs/wgpu/tree/trunk/naga to take the compiled output (Vulkan) SPIR-V and use it to give KernelAbstractions a Web(as in wasm) backend. That won't be possible I guess, because PoCL on Vulkan doesn't support SVM or USM... For the CUDA backend, for now a separate pocl_cuda_jll makes sense. People would just do |
Yeah, that's fine initially. You may want to wait until PoCL 6.1 is released, which requires some changes to the build script in Yggdrasil: JuliaPackaging/Yggdrasil#10317 |
Hello! Not sure if the issue should go here but, I was wondering if Vulkan and CUDA backends could be enabled in PoCL build options (concerning pocl_jll)
The text was updated successfully, but these errors were encountered: