[INFO] fetching crate atomic-int 0.1.2...
[INFO] checking atomic-int-0.1.2 against nightly-2024-02-05 for check-cfg-2
[INFO] extracting crate atomic-int 0.1.2 into /workspace/builds/worker-2-tc1/source
[INFO] validating manifest of crates.io crate atomic-int 0.1.2 on toolchain nightly-2024-02-05
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate atomic-int 0.1.2
[INFO] finished tweaking crates.io crate atomic-int 0.1.2
[INFO] tweaked toml for crates.io crate atomic-int 0.1.2 written to /workspace/builds/worker-2-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 25b6145049ba6a6ab042b246fc59cd8f6488618e8539164f45d8e0825b759b43
[INFO] running `Command { std: "docker" "start" "-a" "25b6145049ba6a6ab042b246fc59cd8f6488618e8539164f45d8e0825b759b43", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "25b6145049ba6a6ab042b246fc59cd8f6488618e8539164f45d8e0825b759b43", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "25b6145049ba6a6ab042b246fc59cd8f6488618e8539164f45d8e0825b759b43", kill_on_drop: false }`
[INFO] [stdout] 25b6145049ba6a6ab042b246fc59cd8f6488618e8539164f45d8e0825b759b43
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 257da0516839250f97a67e64896417960f0f57f2dd820789c2191d943f1f98cf
[INFO] running `Command { std: "docker" "start" "-a" "257da0516839250f97a67e64896417960f0f57f2dd820789c2191d943f1f98cf", kill_on_drop: false }`
[INFO] [stderr]    Compiling atomic-int v0.1.2 (/opt/rustwide/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.69s
[INFO] running `Command { std: "docker" "inspect" "257da0516839250f97a67e64896417960f0f57f2dd820789c2191d943f1f98cf", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "257da0516839250f97a67e64896417960f0f57f2dd820789c2191d943f1f98cf", kill_on_drop: false }`
[INFO] [stdout] 257da0516839250f97a67e64896417960f0f57f2dd820789c2191d943f1f98cf
[INFO] checking atomic-int-0.1.2 against nightly-2024-02-05+rustflags=-Dunexpected_cfgs+cargoflags=-Zcheck-cfg for check-cfg-2
[INFO] extracting crate atomic-int 0.1.2 into /workspace/builds/worker-2-tc2/source
[INFO] validating manifest of crates.io crate atomic-int 0.1.2 on toolchain nightly-2024-02-05
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate atomic-int 0.1.2
[INFO] finished tweaking crates.io crate atomic-int 0.1.2
[INFO] tweaked toml for crates.io crate atomic-int 0.1.2 written to /workspace/builds/worker-2-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] ed18f76d868e8c2eebdb87968833067e4cae46d70d0034e4a341a9673564d45d
[INFO] running `Command { std: "docker" "start" "-a" "ed18f76d868e8c2eebdb87968833067e4cae46d70d0034e4a341a9673564d45d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "ed18f76d868e8c2eebdb87968833067e4cae46d70d0034e4a341a9673564d45d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "ed18f76d868e8c2eebdb87968833067e4cae46d70d0034e4a341a9673564d45d", kill_on_drop: false }`
[INFO] [stdout] ed18f76d868e8c2eebdb87968833067e4cae46d70d0034e4a341a9673564d45d
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-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 -Dunexpected_cfgs" "-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "check" "--frozen" "--all" "--all-targets" "--message-format=json" "-Zcheck-cfg", kill_on_drop: false }`
[INFO] [stdout] 7211c5afa733df5f5584e80afe1e829c3ed242bda1d93f7bdffa7aca8f599e44
[INFO] running `Command { std: "docker" "start" "-a" "7211c5afa733df5f5584e80afe1e829c3ed242bda1d93f7bdffa7aca8f599e44", kill_on_drop: false }`
[INFO] [stderr]    Compiling atomic-int v0.1.2 (/opt/rustwide/workdir)
[INFO] [stdout] error: 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: `debug_assertions`, `doc`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `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`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: requested on the command line with `-D unexpected-cfgs`
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: 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: `debug_assertions`, `doc`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `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`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: requested on the command line with `-D unexpected-cfgs`
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:193:29
[INFO] [stdout]     |
[INFO] [stdout] 193 |         #[cfg(all(not(doc), $cfg))]
[INFO] [stdout]     |                             ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/lib.rs:196:28
[INFO] [stdout]     |
[INFO] [stdout] 196 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 208 | with_c_atomics!(define_c_atomic);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_char_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_char_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_schar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_schar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uchar_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uchar_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_short_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_short_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ushort_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ushort_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_int_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_int_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_uint_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_uint_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_long_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_long_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_longlong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_longlong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: unexpected `cfg` condition name: `has_c_ulonglong_atomic`
[INFO] [stdout]    --> src/fallback/mod.rs:325:28
[INFO] [stdout]     |
[INFO] [stdout] 325 |         #[cfg(any(doc, not($cfg)))]
[INFO] [stdout]     |                            ^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | with_c_atomics!(define_c_fallback);
[INFO] [stdout]     | ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_c_ulonglong_atomic)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error 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] error: aborting due to 33 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 33 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `atomic-int` (lib) due to 34 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stderr] error: could not compile `atomic-int` (lib test) due to 34 previous errors
[INFO] running `Command { std: "docker" "inspect" "7211c5afa733df5f5584e80afe1e829c3ed242bda1d93f7bdffa7aca8f599e44", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "7211c5afa733df5f5584e80afe1e829c3ed242bda1d93f7bdffa7aca8f599e44", kill_on_drop: false }`
[INFO] [stdout] 7211c5afa733df5f5584e80afe1e829c3ed242bda1d93f7bdffa7aca8f599e44
