Repository navigation
Allow UnsafeAtomics 0.4 - #146
Merged
Merged
Conversation
AcceleratedKernels only uses its loads, stores and fences, which 0.4 keeps.
This was referenced Oct 5, 2026
KernelAbstractions main depends on the unregistered KernelInterface 0.4, which it provides through `[sources]`. Julia 1.10 ignores that, so the KA 0.10 job could not resolve its environment there.
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
1 participant
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.
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.4and bumps the version to 0.5.1. The default scope is stillsystemin 0.4. The AMDGPU extension keeps itsAMDGPU.syncscope_agentfence, which AMDGPU.jl continues to define under UnsafeAtomics 0.4 (as the canonicaldevicescope, which GPUCompiler 2.12 emits asagent). With UnsafeAtomics 0.4 and GPUCompiler 2.12,UnsafeAtomics.fence(seq_cst, UnsafeAtomics.device)would be the portable device-scope fence on every back-end. That cleanup is left for later, since it would drop UnsafeAtomics 0.3.The same change for the 0.4 series, as 0.4.4, is in #147; AMDGPU.jl currently allows AcceleratedKernels 0.3.1 and 0.4.
Tested with UnsafeAtomics 0.4.0 and Atomix 1.3.0: the CPU test suite passes (
--cpu, Julia 1.13).