Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

Restrict barrier memory orderings: Likely remove Acquire-only, Release-only #20

Open
dneto0 opened this issue Apr 5, 2019 · 0 comments
Assignees

Comments

@dneto0
Copy link
Contributor

dneto0 commented Apr 5, 2019

General discussion of memory orderings is in gpuweb/gpuweb#232

I proposed not having Acquire-only or Release-only ordering.

(We already agreed that atomics should be Relaxed only. See #16)

@dneto0 dneto0 self-assigned this Apr 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant