[INFO] fetching crate atomic-int 0.1.4...
[INFO] testing atomic-int-0.1.4 against master#1871252fc8bb672d40787e67404e6eaae7059369 for pr-125151
[INFO] extracting crate atomic-int 0.1.4 into /workspace/builds/worker-7-tc1/source
[INFO] validating manifest of crates.io crate atomic-int 0.1.4 on toolchain 1871252fc8bb672d40787e67404e6eaae7059369
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate atomic-int 0.1.4
[INFO] finished tweaking crates.io crate atomic-int 0.1.4
[INFO] tweaked toml for crates.io crate atomic-int 0.1.4 written to /workspace/builds/worker-7-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 2 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 5d4c89c1926f1876117009723fa2d7dce5045ac679b70cfbee6e6e797434f7ce
[INFO] running `Command { std: "docker" "start" "-a" "5d4c89c1926f1876117009723fa2d7dce5045ac679b70cfbee6e6e797434f7ce", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "5d4c89c1926f1876117009723fa2d7dce5045ac679b70cfbee6e6e797434f7ce", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "5d4c89c1926f1876117009723fa2d7dce5045ac679b70cfbee6e6e797434f7ce", kill_on_drop: false }`
[INFO] [stdout] 5d4c89c1926f1876117009723fa2d7dce5045ac679b70cfbee6e6e797434f7ce
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 808a6684a5ec62d6a4b92fa5dca7244fb811e72aa9c0d41b457da9007ec1bcb8
[INFO] running `Command { std: "docker" "start" "-a" "808a6684a5ec62d6a4b92fa5dca7244fb811e72aa9c0d41b457da9007ec1bcb8", kill_on_drop: false }`
[INFO] [stderr]    Compiling atomic-int v0.1.4 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 33 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.59s
[INFO] running `Command { std: "docker" "inspect" "808a6684a5ec62d6a4b92fa5dca7244fb811e72aa9c0d41b457da9007ec1bcb8", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "808a6684a5ec62d6a4b92fa5dca7244fb811e72aa9c0d41b457da9007ec1bcb8", kill_on_drop: false }`
[INFO] [stdout] 808a6684a5ec62d6a4b92fa5dca7244fb811e72aa9c0d41b457da9007ec1bcb8
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] cb9eef6d4917a739803e1288212747daa6e2ed63351ed5d4344e55a7ae4ab8f7
[INFO] running `Command { std: "docker" "start" "-a" "cb9eef6d4917a739803e1288212747daa6e2ed63351ed5d4344e55a7ae4ab8f7", kill_on_drop: false }`
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling atomic-int v0.1.4 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 33 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:328:28
[INFO] [stdout]     |
[INFO] [stdout] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 33 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.24s
[INFO] running `Command { std: "docker" "inspect" "cb9eef6d4917a739803e1288212747daa6e2ed63351ed5d4344e55a7ae4ab8f7", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "cb9eef6d4917a739803e1288212747daa6e2ed63351ed5d4344e55a7ae4ab8f7", kill_on_drop: false }`
[INFO] [stdout] cb9eef6d4917a739803e1288212747daa6e2ed63351ed5d4344e55a7ae4ab8f7
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] c3cea1cbc9b96be3825f6de8524ded5650b0bbb9a26f6bab928254ca7896dec1
[INFO] running `Command { std: "docker" "start" "-a" "c3cea1cbc9b96be3825f6de8524ded5650b0bbb9a26f6bab928254ca7896dec1", kill_on_drop: false }`
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, `windows`
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stderr]    --> src/lib.rs:193:29
[INFO] [stderr]     |
[INFO] [stderr] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stderr]     |                             ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stderr]    --> src/lib.rs:196:28
[INFO] [stderr]     |
[INFO] [stderr] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_atomic` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stderr]    --> src/fallback/mod.rs:328:28
[INFO] [stderr]     |
[INFO] [stderr] 328 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stderr]     |                            ^^^^
[INFO] [stderr] ...
[INFO] [stderr] 337 | with_c_atomics!(define_c_fallback);
[INFO] [stderr]     | ---------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead or adding `println!("cargo::rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `define_c_fallback` which comes from the expansion of the macro `with_c_atomics` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `atomic-int` (lib) generated 33 warnings
[INFO] [stderr] warning: `atomic-int` (lib test) generated 33 warnings (33 duplicates)
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.01s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/atomic_int-a893cf5a46789dbe)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests atomic_int
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "c3cea1cbc9b96be3825f6de8524ded5650b0bbb9a26f6bab928254ca7896dec1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c3cea1cbc9b96be3825f6de8524ded5650b0bbb9a26f6bab928254ca7896dec1", kill_on_drop: false }`
[INFO] [stdout] c3cea1cbc9b96be3825f6de8524ded5650b0bbb9a26f6bab928254ca7896dec1
