diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2022-06-22 15:16:11 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-22 15:16:11 +0900 |
| commit | 25b84491f7fab196d9469753f7261f1b744af25d (patch) | |
| tree | 364fa5a221f5e10dc313baeb4d4d8ca98b7239a3 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | 75a2e5dddd024f3ed98b9c479114782b0b049aa3 (diff) | |
| parent | 4768bfc6ef34de2c2591c96286a958bcd5b40c80 (diff) | |
| download | rust-25b84491f7fab196d9469753f7261f1b744af25d.tar.gz rust-25b84491f7fab196d9469753f7261f1b744af25d.zip | |
Rollup merge of #97516 - RalfJung:atomics, r=joshtriplett
clarify how Rust atomics correspond to C++ atomics ``@cbeuw`` noted in https://github.com/rust-lang/miri/pull/1963 that the correspondence between C++ atomics and Rust atomics is not quite as obvious as one might think, since in Rust I can use `get_mut` to treat previously non-atomic data as atomic. However, I think using C++20 `atomic_ref`, we can establish a suitable relation between the two -- or do you see problems with that ``@cbeuw?`` (I recall you said there was some issue, but it was deep inside that PR and Github makes it impossible to find...) Cc ``@thomcc;`` not sure whom else to ping for atomic memory model things.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
