-
Notifications
You must be signed in to change notification settings - Fork 2
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
implement syncscopes everywhere #20
Conversation
ce6addc
to
0217a90
Compare
0217a90
to
828833a
Compare
@@ -45,4 +47,8 @@ const seq_cst = Internal.seq_cst | |||
const acquire_release = acq_rel | |||
const sequentially_consistent = seq_cst | |||
|
|||
# SyncScope | |||
const none = Internal.none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have an alias for this called system
?
@maleadt so the last remaining question is what do we do about the GPU backend specific syncscopes.
|
What about leaving it up to the caller and simply using symbols? I'm not sure how we'll be able to generalize this without some input from the back-end anyway (i.e. Metal.jl specifying which syncscope to use for a certain kind of array). |
Yeah, right now, I allow for anything to be wrapped in |
TODO