[INFO] fetching crate atomic-int 0.1.4...
[INFO] checking atomic-int-0.1.4 against try#47af3d0de9d26c7deba4cfb203b710cc3f764e91 for pr-130443
[INFO] extracting crate atomic-int 0.1.4 into /workspace/builds/worker-0-tc2/source
[INFO] validating manifest of crates.io crate atomic-int 0.1.4 on toolchain 47af3d0de9d26c7deba4cfb203b710cc3f764e91
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+47af3d0de9d26c7deba4cfb203b710cc3f764e91" "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-0-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+47af3d0de9d26c7deba4cfb203b710cc3f764e91" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 1 package to latest compatible version
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+47af3d0de9d26c7deba4cfb203b710cc3f764e91" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/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:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+47af3d0de9d26c7deba4cfb203b710cc3f764e91" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 6713846cc39b15be40b9732cba533c30fe8d45195eb6e585dcb6185589881b65
[INFO] running `Command { std: "docker" "start" "-a" "6713846cc39b15be40b9732cba533c30fe8d45195eb6e585dcb6185589881b65", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "6713846cc39b15be40b9732cba533c30fe8d45195eb6e585dcb6185589881b65", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "6713846cc39b15be40b9732cba533c30fe8d45195eb6e585dcb6185589881b65", kill_on_drop: false }`
[INFO] [stdout] 6713846cc39b15be40b9732cba533c30fe8d45195eb6e585dcb6185589881b65
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/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:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+47af3d0de9d26c7deba4cfb203b710cc3f764e91" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] da70a938e16108fe61378d8b81e43d4859b08d2f6e7eb02e5e89c05c4f210424
[INFO] running `Command { std: "docker" "start" "-a" "da70a938e16108fe61378d8b81e43d4859b08d2f6e7eb02e5e89c05c4f210424", 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`, `fmt_debug`, `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`, and `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_char_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_char_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_schar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_schar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uchar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uchar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_short_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_short_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ushort_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ushort_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_int_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_int_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uint_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uint_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_long_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_long_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_longlong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_longlong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulonglong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulonglong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_char_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_schar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uchar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_short_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ushort_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_int_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uint_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_long_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_longlong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulonglong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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_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`, `fmt_debug`, `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`, and `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_char_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_char_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_schar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_schar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uchar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uchar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_short_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_short_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ushort_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ushort_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_int_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_int_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uint_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uint_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_long_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_long_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_longlong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_longlong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulonglong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulonglong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_char_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_schar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uchar_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_short_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ushort_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_int_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_uint_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_long_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_longlong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(has_c_ulonglong_atomic)'] }
[INFO] [stdout]     = help: or consider 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/rustc/check-cfg/cargo-specifics.html> 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: 33 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.48s
[INFO] running `Command { std: "docker" "inspect" "da70a938e16108fe61378d8b81e43d4859b08d2f6e7eb02e5e89c05c4f210424", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "da70a938e16108fe61378d8b81e43d4859b08d2f6e7eb02e5e89c05c4f210424", kill_on_drop: false }`
[INFO] [stdout] da70a938e16108fe61378d8b81e43d4859b08d2f6e7eb02e5e89c05c4f210424
