diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2022-07-06 20:43:23 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-06 20:43:23 +0200 |
| commit | 4755173cf61dfd432d8fb96ea3d09da99fe30283 (patch) | |
| tree | a22f929eb63cecca112b3003f5968dc7c476f8cd /compiler/rustc_codegen_llvm/src/asm.rs | |
| parent | 049308cf8b48e9d67e54d6d0b01c10c79d1efc3a (diff) | |
| parent | e65ecee90eff2c90e12164417cc31ab959c321cf (diff) | |
| download | rust-4755173cf61dfd432d8fb96ea3d09da99fe30283.tar.gz rust-4755173cf61dfd432d8fb96ea3d09da99fe30283.zip | |
Rollup merge of #96935 - thomcc:atomicptr-strict-prov, r=dtolnay
Allow arithmetic and certain bitwise ops on AtomicPtr This is mainly to support migrating from `AtomicUsize`, for the strict provenance experiment. This is a pretty dubious set of APIs, but it should be sufficient to allow code that's using `AtomicUsize` to manipulate a tagged pointer atomically. It's under a new feature gate, `#![feature(strict_provenance_atomic_ptr)]`, but I'm not sure if it needs its own tracking issue. I'm happy to make one, but it's not clear that it's needed. I'm unsure if it needs changes in the various non-LLVM backends. Because we just cast things to integers anyway (and were already doing so), I doubt it. API change proposal: https://github.com/rust-lang/libs-team/issues/60 Fixes #95492
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/asm.rs')
0 files changed, 0 insertions, 0 deletions