diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-06-12 00:05:27 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-12 00:05:27 +0200 |
| commit | 3b41e54799754fcdc7ae0429bd8fd64b5bd5a1fd (patch) | |
| tree | fa1715c20e5609f61c4cf414a94b3263ac15dd16 /library/std/src/sys/unix/stack_overflow.rs | |
| parent | 2e42476267011bd8937dfcc0f707aa08e34d54d9 (diff) | |
| parent | 05b2d3f7dc623fc5304fa0edc9efeaf08ea1db26 (diff) | |
| download | rust-3b41e54799754fcdc7ae0429bd8fd64b5bd5a1fd.tar.gz rust-3b41e54799754fcdc7ae0429bd8fd64b5bd5a1fd.zip | |
Rollup merge of #73036 - alexcrichton:update-wasm-fence, r=Mark-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. Closes #65687 Closes #72997
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions