You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
poliorcetics opened this issue
Jun 4, 2020
· 0 comments
· Fixed by #73036
Labels
C-bugCategory: This is a bug.O-wasmTarget: WASM (WebAssembly), http://webassembly.org/T-libsRelevant to the library team, which will review and decide on the PR/issue.
The text was updated successfully, but these errors were encountered:
jonas-schievink
added
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
O-wasm
Target: WASM (WebAssembly), http://webassembly.org/
labels
Jun 4, 2020
…ark-Simulacrum
std: Enable atomic.fence emission on wasm32
This commit removes the `#[cfg]` guards in `atomic::fence` on wasm
targets. Since these guards were originally added the upstream wasm
specification for threads gained an `atomic.fence` instruction, so LLVM
no longer panics on these intrinsics.
Although there aren't a ton of tests in-repo for this right now I've
tested locally and all of these fences generate `atomic.fence`
instructions in wasm.
Closesrust-lang#65687Closesrust-lang#72997
C-bugCategory: This is a bug.O-wasmTarget: WASM (WebAssembly), http://webassembly.org/T-libsRelevant to the library team, which will review and decide on the PR/issue.
The function
pub fence(order: Ordering)
inlibcore/sync/atomic.rs
does nothing when compiled for Web Assembly.This stem from an old issue in web assembly #WebAssembly/tool-conventions/issues/59 and LLVM crashing (at the time) with it.
This has since been fixed, notably for LLVM, maybe we can remove the
#[cfg(...)]
and comment about it ?The text was updated successfully, but these errors were encountered: