diff options
| author | bors <bors@rust-lang.org> | 2016-08-02 23:32:31 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-02 23:32:31 -0700 |
| commit | ea07d52676a68aff3e85599469523a25eeb1afbf (patch) | |
| tree | edb5ffb3c725b1da8ff6ee628d14b90a753f83d6 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | f495483f2d44bdf94c9dbd78efa80b02f42b2b23 (diff) | |
| parent | 5f8010443153036c887c917e1580e6af2d296361 (diff) | |
| download | rust-ea07d52676a68aff3e85599469523a25eeb1afbf.tar.gz rust-ea07d52676a68aff3e85599469523a25eeb1afbf.zip | |
Auto merge of #35176 - japaric:no-atomics, r=alexcrichton
core: fix `cargo build` for targets with "max-atomic-width": 0 This crate was failing to compile due to dead_code/unused_imports warnings. This commits disables these two lints for these targets. --- r? @alexcrichton cc @Amanieu is `cfg(target_has_atomic = "8")` the right `cfg` to use? I think that all targets that support some form of atomics will at a minimum support byte level atomics. FWIW, the only thing that's left in `sync::atomic` for these targets is `Ordering` and the `fence` function.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions