[INFO] fetching crate atomic-int 0.1.4... [INFO] checking atomic-int-0.1.4 against try#998b6603a58e47f42ccce7a67943234e96b6839e for pr-143170 [INFO] extracting crate atomic-int 0.1.4 into /workspace/builds/worker-2-tc2/source [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-2-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate atomic-int 0.1.4 on toolchain 998b6603a58e47f42ccce7a67943234e96b6839e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+998b6603a58e47f42ccce7a67943234e96b6839e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+998b6603a58e47f42ccce7a67943234e96b6839e" "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" "+998b6603a58e47f42ccce7a67943234e96b6839e" "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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+998b6603a58e47f42ccce7a67943234e96b6839e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 6e890cadde6cd1c2107a63dfbaca3f71f282aed5760389001e06caef6ff2609c [INFO] running `Command { std: "docker" "start" "-a" "6e890cadde6cd1c2107a63dfbaca3f71f282aed5760389001e06caef6ff2609c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "6e890cadde6cd1c2107a63dfbaca3f71f282aed5760389001e06caef6ff2609c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6e890cadde6cd1c2107a63dfbaca3f71f282aed5760389001e06caef6ff2609c", kill_on_drop: false }` [INFO] [stdout] 6e890cadde6cd1c2107a63dfbaca3f71f282aed5760389001e06caef6ff2609c [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" "-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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+998b6603a58e47f42ccce7a67943234e96b6839e" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 2f154379ed6a5bbdf1471eb129a925a797da285e432b1961164f19e583a6132c [INFO] running `Command { std: "docker" "start" "-a" "2f154379ed6a5bbdf1471eb129a925a797da285e432b1961164f19e583a6132c", 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: `docsrs`, `feature`, and `test` and 31 more [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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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: `docsrs`, `feature`, and `test` and 31 more [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 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 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 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 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 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 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 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 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 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 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/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 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 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 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/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 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 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/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 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/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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.40s [INFO] running `Command { std: "docker" "inspect" "2f154379ed6a5bbdf1471eb129a925a797da285e432b1961164f19e583a6132c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2f154379ed6a5bbdf1471eb129a925a797da285e432b1961164f19e583a6132c", kill_on_drop: false }` [INFO] [stdout] 2f154379ed6a5bbdf1471eb129a925a797da285e432b1961164f19e583a6132c