Repository navigation
[release-0.4] Backports for 0.4.4 - #147
Merged
Merged
Conversation
Merged
(cherry picked from commit e641c28)
* Update Buildkite pipeline for the new JuliaGPU cluster. Switch to the per-backend queues of the new JuliaGPU cluster. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Move the Metal job(s) to the new metal queue. The JuliaGPU cluster now has a macOS agent with an Apple Silicon GPU, so Metal jobs no longer need a separate pipeline on the ecosystem cluster. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit a76bf7b)
The back-end can need different versions of AcceleratedKernels' dependencies, e.g. OpenCL still requires UnsafeAtomics 0.3. Adding it after those were loaded left the session with mismatched packages. Also use the registered OpenCL.jl, as its master branch is gone.
AcceleratedKernels only uses its loads, stores and fences, which 0.4 keeps.
maleadt
force-pushed
the
tb/unsafeatomics-0.4-backport
branch
from
October 6, 2026 05:16
08abd48 to
03ce906
Compare
maleadt
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backports for a 0.4.4 release.
UnsafeAtomics 0.4 is out, and Atomix 1.3 and the GPU back-ends (starting with AMDGPU.jl) move to it. Every AcceleratedKernels release since 0.4.3 caps UnsafeAtomics at 0.3, so environments that need 0.4 either fail to resolve or fall back to AcceleratedKernels 0.4.2. AcceleratedKernels only uses UnsafeAtomics'
load,store!andfence, which 0.4 keeps, so this widens the bound to0.3, 0.4, as #146 does for 0.5.1. The scan's fences use the default scope, which is stillsystemin 0.4. AMDGPU.jl currently allows AcceleratedKernels 0.3.1 and 0.4, which is why the 0.4 series needs this too.The branch was cut from v0.4.3, so CI needed fixes before it could run:
juliagpuqueue, which no longer exists;masterbranch, which is gone. Using the registered version exposed another problem: the tests installed the back-end after loading AcceleratedKernels, and OpenCL still requires UnsafeAtomics 0.3, so the session ended up with mismatched packages. The back-end is now installed before anything is loaded.Tested with UnsafeAtomics 0.4.0 and Atomix 1.3.0: the CPU and OpenCL (PoCL) test suites pass on Julia 1.13, and so do AMDGPU.jl's sorting and array tests on a gfx1036 GPU, with AMDGPU.jl ported to UnsafeAtomics 0.4.