diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2023-01-23 19:29:58 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-23 19:29:58 +0900 |
| commit | 9e79642a7b0578f69585fc59476b5269f6040c5a (patch) | |
| tree | 904ddbe19d8c922d6576ba9630c64bee8bc77047 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 6b3cd03fdb285781c60f5962194719fdfd46d910 (diff) | |
| parent | 651e8734620a07d25acab4a594e23e33b4d91f50 (diff) | |
| download | rust-9e79642a7b0578f69585fc59476b5269f6040c5a.tar.gz rust-9e79642a7b0578f69585fc59476b5269f6040c5a.zip | |
Rollup merge of #106796 - vadorovsky:revert-105708-enable-atomic-cas-bpf, r=bjorn3
BPF: Disable atomic CAS Enabling CAS for BPF targets (https://github.com/rust-lang/rust/pull/105708) breaks the build of core library. The failure occurs both when building rustc for BPF targets and when building crates for BPF targets with the current nightly. The LLVM BPF backend does not correctly lower all `atomicrmw` operations and crashes for unsupported ones. Before we can enable CAS for BPF in Rust, we need to fix the LLVM BPF backend first. Fixes #106795 Signed-off-by: Michal Rostecki <vadorovsky@gmail.com>
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions