diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-08-08 03:30:55 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-08-08 03:30:55 +0200 |
| commit | 6f36f1ffbd7421783cc753d7566bcb2978099cb2 (patch) | |
| tree | f6452b7764e4e8e005373916c18f03f2169651d6 /compiler/rustc_codegen_llvm/src/context.rs | |
| parent | 42cdc7df2088d06ce76d3aa84780e25aff1993d8 (diff) | |
| parent | b47e4a46c62fc6f9048d457aa9636db1550f3eaa (diff) | |
| download | rust-6f36f1ffbd7421783cc753d7566bcb2978099cb2.tar.gz rust-6f36f1ffbd7421783cc753d7566bcb2978099cb2.zip | |
Rollup merge of #114497 - taiki-e:revert-riscv-atomic, r=Amanieu
Revert #98333 "Re-enable atomic loads and stores for all RISC-V targets" This reverts #98333. As said in https://github.com/rust-lang/rust/pull/98333#issuecomment-1666375293, `forced-atomics` target feature is also needed to enable atomic load/store on these targets (otherwise, libcalls are generated): https://godbolt.org/z/433qeG7vd However, `forced-atomics` target feature is currently broken (https://github.com/rust-lang/rust/issues/114153), so AFAIK, there is currently no way to enable atomic load/store (via core::intrinsics) on these targets properly. r? `@Amanieu`
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/context.rs')
0 files changed, 0 insertions, 0 deletions