diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-09-02 22:35:19 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-02 22:35:19 +0200 |
| commit | f0072bf2740965e789eba92db46208a34e1d4fa1 (patch) | |
| tree | c9920482ad0d19996cb1cabb6384ebf876bfa476 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | c6410f506698b09a44a667c40260e90b5d0e91e7 (diff) | |
| parent | 32a30dd00551dfb6ac36fd2b29b97f0933283b02 (diff) | |
| download | rust-f0072bf2740965e789eba92db46208a34e1d4fa1.tar.gz rust-f0072bf2740965e789eba92db46208a34e1d4fa1.zip | |
Rollup merge of #129856 - RalfJung:compiler_fence, r=thomcc
compiler_fence documentation: emphasize synchronization, not reordering Our `fence` docs have at some point been update to explain that they are about synchronization, not about "preventing reordering". This updates the `compiler_fence` docs n the same vein, mostly by referring to the `fence` docs. The old docs make it sound like I can put a compiler_fence in the middle of a bunch of non-atomic operations and that would achieve any kind of guarantee. It does not, atomic operations are still required to do synchronization. I also slightly tweaked the `fence` docs, to put the synchronization first and the "prevent reordering" second. Cc `@rust-lang/opsem` `@chorman0773` `@m-ou-se` Fixes https://github.com/rust-lang/rust/issues/129189 Fixes https://github.com/rust-lang/rust/issues/54962
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions