diff options
| author | Corey Farwell <coreyf@rwell.org> | 2017-04-17 23:21:17 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-17 23:21:17 -0400 |
| commit | b8c446eab808a16ea6e878171762d5a1a58ac927 (patch) | |
| tree | 0d81675631071a739589e5c435881e76aec64ef8 /src/rustllvm/RustWrapper.cpp | |
| parent | 235fe8313fd0ffec665f1400da781ab2cb1e13f9 (diff) | |
| parent | 368d56010ae91a8b136c9eea5821ff3e5a7b79d3 (diff) | |
| download | rust-b8c446eab808a16ea6e878171762d5a1a58ac927.tar.gz rust-b8c446eab808a16ea6e878171762d5a1a58ac927.zip | |
Rollup merge of #41262 - jonhoo:compiler-barrier-rename, r=alexcrichton
Rename compiler_barrier to compiler_fence This addresses concerns raised following the merge of #41092. Specifically: > The naming of these seems surprising: the multithreaded functions (and both the single and multithreaded intrinsics themselves) are fences, but this is a barrier. It's not incorrect, but the latter is both inconsistent with the existing functions and slightly confusing with another type in std (e.g., `Barrier`). `compiler_fence` carries the same semantic implication that this is a compiler-only operation, while being more in line with the fence/barrier concepts already in use in `std`.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions