Targeting Vulkan through Rusticl/Zink
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- julia
- Domain
- build-system, computer-graphics
Research direction
Start by investigating the existing Mesa Homebrew package and how JLLs are built for JuliaGPU projects. The issue calls for minimal Mesa builds with Rusticl and Zink plus MoltenVK, while determining whether LLVM is required. Done means usable JLLs that let OpenCL.jl run on Macs without the unsupported LLVM dependency.
Written by the indexing model from the issue text.
Description
The mesa homebrew package links against an unsupported version of LLVM.
This makes it unusable to run OpenCL.jl on Macs.
This can be achieved by building a JLL for:
- Mesa (Zink + Rusticl)
- MoltenVK
Some points:
- We need a minimal build of Mesa with only Rusticl and Zink supported. I'm not sure if llvm is a required dependency here.
- MoltenVK doesn't seem to have a direct dependency on LLVM.
Building Mesa (Zink + Rusticl) also has the advantage to support many more GPUs than Apple like Qualcomm, Mediatek, Rockchip etc (anything with good enough Vulkan support)
- Dominant language
- Julia
- Stars
- 313
- Forks
- 50
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 44
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from JuliaGPU/OpenCL.jl
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
A failed SVM allocation returns a CLArray at address 0, and kernels that write to it fault the GPUOpen
Difficulty 3/5 1-2 days Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
kernels latency regression
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in JuliaGPU/OpenCL.jl
Similar issues
-
`SplitRungeKutta` time steppers never call `update_lagrangian_particle_state!`, so particle `tracked_fields` are never updatedPossibly taken @ali-ramadhan claimed this today. Openbug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
CliMA/Oceananigans.jl#6381 ·
Maintainers usually reply within 1 day
-
ci system:windows test
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Single-column TKE example: boundary-layer depth description doesn't match Han & Bretherton (2019)Open
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
NumericalEarth/Breeze.jl#1143 ·
Maintainers usually reply within 1 day
-
format-check (Runic) is red on master: formatter drift on ~200 filesPossibly taken @ChrisRackauckas-Claude claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
SciML/ModelingToolkit.jl#5337 · 1 comment ·
Maintainers usually reply within 3 days
-
bug parsers
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lanl-ansi/GasModels.jl#366 ·