diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-11-20 20:10:14 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-20 20:10:14 +0100 |
| commit | 1099bc8e735430d860c7dc410024108f78d4c28b (patch) | |
| tree | e83bcd7b3a74c351b0d7381ab4dcb5a0fd426502 /library/std/src/lib.rs | |
| parent | fbed195b4df1a21aee835e68efa88e8f4c4e0d4a (diff) | |
| parent | f37d021d6ccb7949ba8e8b2a5d6e91686063da2a (diff) | |
| download | rust-1099bc8e735430d860c7dc410024108f78d4c28b.tar.gz rust-1099bc8e735430d860c7dc410024108f78d4c28b.zip | |
Rollup merge of #133244 - daxpedda:wasm32v1-none-atomic, r=alexcrichton
Account for `wasm32v1-none` when exporting TLS symbols Exporting TLS related symbols was limited to `wasm32-unknown-unknown` because WASI and Emscripten (?) have their own infrastructure to deal with TLS. However, the introduction of `wasm32v1-none` is in the same boat as `wasm32-unknown-unknown`. This PR adjust the mechanism to account for `wasm32v1-none` as well. See https://github.com/rust-lang/rust/pull/102385 and https://github.com/rust-lang/rust/pull/102440. r? ``@alexcrichton``
Diffstat (limited to 'library/std/src/lib.rs')
0 files changed, 0 insertions, 0 deletions