We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
fence
UnsafeAtomics.jl now relies on Base for fence:
UnsafeAtomics.jl/ext/UnsafeAtomicsLLVM/atomics.jl
Line 196 in 2eaec48
That seems wrong, fence has been renamed to Threads.atomic_fence now (without an order argument): https://github.com/JuliaLang/julia/blob/447dc2d8e9a71669c6a3f62ff8ac71054c811a94/base/atomics.jl#L465-L468
Threads.atomic_fence
We should probably add fence to the interface here, and add a proper implementation that supports arbitrary orderings and synchronization scopes.
The text was updated successfully, but these errors were encountered:
Fixed the first part, the second part is a bit more work :)
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
UnsafeAtomics.jl now relies on Base for
fence
:UnsafeAtomics.jl/ext/UnsafeAtomicsLLVM/atomics.jl
Line 196 in 2eaec48
That seems wrong,
fence
has been renamed toThreads.atomic_fence
now (without an order argument): https://github.com/JuliaLang/julia/blob/447dc2d8e9a71669c6a3f62ff8ac71054c811a94/base/atomics.jl#L465-L468We should probably add
fence
to the interface here, and add a proper implementation that supports arbitrary orderings and synchronization scopes.The text was updated successfully, but these errors were encountered: