-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
SSE1 support does not have _mm_sfence(). #3051
Labels
Comments
juj
added a commit
to juj/emscripten
that referenced
this issue
Jun 20, 2015
Merged
juj
added a commit
to juj/emscripten
that referenced
this issue
Jun 25, 2015
juj
added a commit
to juj/emscripten
that referenced
this issue
Aug 10, 2015
juj
added a commit
to juj/emscripten
that referenced
this issue
Aug 15, 2015
juj
added a commit
to juj/emscripten
that referenced
this issue
Aug 15, 2015
juj
added a commit
to juj/emscripten
that referenced
this issue
Aug 16, 2015
juj
added a commit
to juj/emscripten
that referenced
this issue
Aug 17, 2015
SSE1 and SSE2 fences have been implemented as full barriers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SSE1 has an explicit SIMD fence operation that guarantees synchronization between threads. Currently this is not observable in JS and so for all purposes, this can be a no-op, but in the future with the SharedArrayBuffer work, this will be observable. Marking down this issue to discuss if we can support this at some point?
The text was updated successfully, but these errors were encountered: