[INFO] fetching crate core_detect 1.0.0...
[INFO] checking core_detect-1.0.0 against try#987a165cfab916796a8315782b83ac460a651ce2 for pr-145262
[INFO] extracting crate core_detect 1.0.0 into /workspace/builds/worker-1-tc2/source
[INFO] started tweaking crates.io crate core_detect 1.0.0
[INFO] finished tweaking crates.io crate core_detect 1.0.0
[INFO] tweaked toml for crates.io crate core_detect 1.0.0 written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate core_detect 1.0.0 on toolchain 987a165cfab916796a8315782b83ac460a651ce2
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "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" "+987a165cfab916796a8315782b83ac460a651ce2" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 5 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded cupid v0.6.1
[INFO] [stderr] error: No space left on device (os error 28)
[INFO] checking core_detect-1.0.0 against try#987a165cfab916796a8315782b83ac460a651ce2 for pr-145262
[INFO] extracting crate core_detect 1.0.0 into /workspace/builds/worker-1-tc2/source
[INFO] started tweaking crates.io crate core_detect 1.0.0
[INFO] finished tweaking crates.io crate core_detect 1.0.0
[INFO] tweaked toml for crates.io crate core_detect 1.0.0 written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate core_detect 1.0.0 on toolchain 987a165cfab916796a8315782b83ac460a651ce2
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "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" "+987a165cfab916796a8315782b83ac460a651ce2" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr] error: failed to write /workspace/builds/worker-1-tc2/source/Cargo.lock
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   No space left on device (os error 28)
[INFO] checking core_detect-1.0.0 against try#987a165cfab916796a8315782b83ac460a651ce2 for pr-145262
[INFO] extracting crate core_detect 1.0.0 into /workspace/builds/worker-1-tc2/source
[INFO] started tweaking crates.io crate core_detect 1.0.0
[INFO] finished tweaking crates.io crate core_detect 1.0.0
[INFO] tweaked toml for crates.io crate core_detect 1.0.0 written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate core_detect 1.0.0 on toolchain 987a165cfab916796a8315782b83ac460a651ce2
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "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" "+987a165cfab916796a8315782b83ac460a651ce2" "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] [stderr]      Locking 5 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded cupid v0.6.1
[INFO] [stderr] error: No space left on device (os error 28)
[INFO] checking core_detect-1.0.0 against try#987a165cfab916796a8315782b83ac460a651ce2 for pr-145262
[INFO] extracting crate core_detect 1.0.0 into /workspace/builds/worker-1-tc2/source
[INFO] started tweaking crates.io crate core_detect 1.0.0
[INFO] finished tweaking crates.io crate core_detect 1.0.0
[INFO] tweaked toml for crates.io crate core_detect 1.0.0 written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate core_detect 1.0.0 on toolchain 987a165cfab916796a8315782b83ac460a651ce2
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "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" "+987a165cfab916796a8315782b83ac460a651ce2" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 5 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded cupid v0.6.1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 97cf10cbf3fa51f6450039f38741661c50dd69c2b5ddac4a8eb6b074a7a3b348
[INFO] running `Command { std: "docker" "start" "-a" "97cf10cbf3fa51f6450039f38741661c50dd69c2b5ddac4a8eb6b074a7a3b348", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "97cf10cbf3fa51f6450039f38741661c50dd69c2b5ddac4a8eb6b074a7a3b348", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "97cf10cbf3fa51f6450039f38741661c50dd69c2b5ddac4a8eb6b074a7a3b348", kill_on_drop: false }`
[INFO] [stdout] 97cf10cbf3fa51f6450039f38741661c50dd69c2b5ddac4a8eb6b074a7a3b348
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+987a165cfab916796a8315782b83ac460a651ce2" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] d1e898f162ef5e1114bf592d376bcef4bdae5b44c7d45bb144567080f5615a68
[INFO] running `Command { std: "docker" "start" "-a" "d1e898f162ef5e1114bf592d376bcef4bdae5b44c7d45bb144567080f5615a68", kill_on_drop: false }`
[INFO] [stderr]    Compiling semver-parser v0.7.0
[INFO] [stderr]    Compiling gcc v0.3.55
[INFO] [stderr]     Checking core_detect v1.0.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `std_detect_env_override`
[INFO] [stdout]    --> src/macros.rs:70:19
[INFO] [stdout]     |
[INFO] [stdout]  70 |               #[cfg(feature = "std_detect_env_override")]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `assume_has_cpuid`, `default`, and `unstable_has_cpuid`
[INFO] [stdout]     = help: consider adding `std_detect_env_override` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tsc`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `mmx`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512er`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512f"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512pf`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512f"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512gfni`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512vnni"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512vaes`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512vl"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512vpclmulqdq`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary transmute
[INFO] [stdout]   --> src/os/x86.rs:97:13
[INFO] [stdout]    |
[INFO] [stdout] 97 |             mem::transmute(ebx),
[INFO] [stdout]    |             --------------^^^^^
[INFO] [stdout]    |             |
[INFO] [stdout]    |             help: replace this with: `u32::to_ne_bytes`
[INFO] [stdout]    |
[INFO] [stdout]    = help: there's also `to_le_bytes` and `to_be_bytes` if you expect a particular byte order
[INFO] [stdout]    = note: `#[warn(unnecessary_transmutes)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary transmute
[INFO] [stdout]   --> src/os/x86.rs:98:13
[INFO] [stdout]    |
[INFO] [stdout] 98 |             mem::transmute(edx),
[INFO] [stdout]    |             --------------^^^^^
[INFO] [stdout]    |             |
[INFO] [stdout]    |             help: replace this with: `u32::to_ne_bytes`
[INFO] [stdout]    |
[INFO] [stdout]    = help: there's also `to_le_bytes` and `to_be_bytes` if you expect a particular byte order
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary transmute
[INFO] [stdout]   --> src/os/x86.rs:99:13
[INFO] [stdout]    |
[INFO] [stdout] 99 |             mem::transmute(ecx),
[INFO] [stdout]    |             --------------^^^^^
[INFO] [stdout]    |             |
[INFO] [stdout]    |             help: replace this with: `u32::to_ne_bytes`
[INFO] [stdout]    |
[INFO] [stdout]    = help: there's also `to_le_bytes` and `to_be_bytes` if you expect a particular byte order
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling semver v0.9.0
[INFO] [stderr]    Compiling rustc_version v0.2.3
[INFO] [stderr]    Compiling cupid v0.6.1
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 20 |     check_feature!("aes");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 21 |     check_feature!("pclmulqdq");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 22 |     check_feature!("rdrand");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 23 |     check_feature!("rdseed");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 24 |     check_feature!("tsc");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 25 |     check_feature!("sse");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 26 |     check_feature!("sse2");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 27 |     check_feature!("sse3");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 28 |     check_feature!("ssse3");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 29 |     check_feature!("sse4.1");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 30 |     check_feature!("sse4.2");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 31 |     check_feature!("sse4a");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 32 |     check_feature!("sha");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 33 |     check_feature!("avx");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 34 |     check_feature!("avx2");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 35 |     check_feature!("avx512f");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 36 |     check_feature!("avx512cd");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 37 |     check_feature!("avx512er");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 38 |     check_feature!("avx512pf");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 39 |     check_feature!("avx512bw");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 40 |     check_feature!("avx512dq");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 41 |     check_feature!("avx512vl");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 42 |     check_feature!("avx512ifma");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 43 |     check_feature!("avx512vbmi");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 44 |     check_feature!("avx512vpopcntdq");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 45 |     check_feature!("fma");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 46 |     check_feature!("bmi1");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 47 |     check_feature!("bmi2");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 48 |     check_feature!("popcnt");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 49 |     check_feature!("abm");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 50 |     check_feature!("tbm");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 51 |     check_feature!("lzcnt");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 52 |     check_feature!("xsave");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 53 |     check_feature!("xsaveopt");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 54 |     check_feature!("xsavec");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_std.rs:6:21
[INFO] [stdout]    |
[INFO] [stdout]  6 |             if cfg!(allow_false_negative) {
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 55 |     check_feature!("xsaves");
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `std_detect_env_override`
[INFO] [stdout]    --> src/macros.rs:70:19
[INFO] [stdout]     |
[INFO] [stdout]  70 |               #[cfg(feature = "std_detect_env_override")]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `assume_has_cpuid`, `default`, and `unstable_has_cpuid`
[INFO] [stdout]     = help: consider adding `std_detect_env_override` as a feature in `Cargo.toml`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `tsc`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `mmx`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512er`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512f"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512pf`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512f"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512gfni`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512vnni"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512vaes`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^------------
[INFO] [stdout]     |                                             |
[INFO] [stdout]     |                                             help: there is a expected value with a similar name: `"avx512vl"`
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `avx512vpclmulqdq`
[INFO] [stdout]    --> src/macros.rs:94:26
[INFO] [stdout]     |
[INFO] [stdout]  94 |                       cfg!(target_feature = $feature_lit) ||
[INFO] [stdout]     |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/arch/x86.rs:18:1
[INFO] [stdout]     |
[INFO] [stdout]  18 | / features! {
[INFO] [stdout]  19 | |     @TARGET: x86;
[INFO] [stdout]  20 | |     @MACRO_NAME: is_x86_feature_detected;
[INFO] [stdout]  21 | |     @MACRO_ATTRS:
[INFO] [stdout] ...   |
[INFO] [stdout] 194 | |     /// RTM, Intel (Restricted Transactional Memory)
[INFO] [stdout] 195 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_feature` are: `10e60`, `2e3`, `3e3r1`, `3e3r2`, `3e3r3`, `3e7`, `7e10`, `a`, `aclass`, `adx`, `aes`, `altivec`, `alu32`, `amx-avx512`, `amx-bf16`, `amx-complex`, `amx-fp16`, `amx-fp8`, `amx-int8`, `amx-movrs`, `amx-tf32`, `amx-tile`, `amx-transpose`, `apxf`, `atomics`, `avx`, `avx10.1`, `avx10.2`, `avx2`, `avx512bf16`, `avx512bitalg`, `avx512bw`, `avx512cd`, `avx512dq`, and `avx512f` and 425 more
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `features` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 22 | /     check_feature!(
[INFO] [stdout] 23 | |         core_detect::is_x86_feature_detected!("aes"),
[INFO] [stdout] 24 | |         information.aesni()
[INFO] [stdout] 25 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 26 | /     check_feature!(
[INFO] [stdout] 27 | |         core_detect::is_x86_feature_detected!("pclmulqdq"),
[INFO] [stdout] 28 | |         information.pclmulqdq()
[INFO] [stdout] 29 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 30 | /     check_feature!(
[INFO] [stdout] 31 | |         core_detect::is_x86_feature_detected!("rdrand"),
[INFO] [stdout] 32 | |         information.rdrand()
[INFO] [stdout] 33 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 34 | /     check_feature!(
[INFO] [stdout] 35 | |         core_detect::is_x86_feature_detected!("rdseed"),
[INFO] [stdout] 36 | |         information.rdseed()
[INFO] [stdout] 37 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 38 | /     check_feature!(
[INFO] [stdout] 39 | |         core_detect::is_x86_feature_detected!("tsc"),
[INFO] [stdout] 40 | |         information.tsc()
[INFO] [stdout] 41 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 42 | /     check_feature!(
[INFO] [stdout] 43 | |         core_detect::is_x86_feature_detected!("sse"),
[INFO] [stdout] 44 | |         information.sse()
[INFO] [stdout] 45 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 46 | /     check_feature!(
[INFO] [stdout] 47 | |         core_detect::is_x86_feature_detected!("sse2"),
[INFO] [stdout] 48 | |         information.sse2()
[INFO] [stdout] 49 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 50 | /     check_feature!(
[INFO] [stdout] 51 | |         core_detect::is_x86_feature_detected!("sse3"),
[INFO] [stdout] 52 | |         information.sse3()
[INFO] [stdout] 53 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 54 | /     check_feature!(
[INFO] [stdout] 55 | |         core_detect::is_x86_feature_detected!("ssse3"),
[INFO] [stdout] 56 | |         information.ssse3()
[INFO] [stdout] 57 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 58 | /     check_feature!(
[INFO] [stdout] 59 | |         core_detect::is_x86_feature_detected!("sse4.1"),
[INFO] [stdout] 60 | |         information.sse4_1()
[INFO] [stdout] 61 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 62 | /     check_feature!(
[INFO] [stdout] 63 | |         core_detect::is_x86_feature_detected!("sse4.2"),
[INFO] [stdout] 64 | |         information.sse4_2()
[INFO] [stdout] 65 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 66 | /     check_feature!(
[INFO] [stdout] 67 | |         core_detect::is_x86_feature_detected!("sse4a"),
[INFO] [stdout] 68 | |         information.sse4a()
[INFO] [stdout] 69 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 70 | /     check_feature!(
[INFO] [stdout] 71 | |         core_detect::is_x86_feature_detected!("sha"),
[INFO] [stdout] 72 | |         information.sha()
[INFO] [stdout] 73 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 74 | /     check_feature!(
[INFO] [stdout] 75 | |         core_detect::is_x86_feature_detected!("avx"),
[INFO] [stdout] 76 | |         information.avx()
[INFO] [stdout] 77 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 78 | /     check_feature!(
[INFO] [stdout] 79 | |         core_detect::is_x86_feature_detected!("avx2"),
[INFO] [stdout] 80 | |         information.avx2()
[INFO] [stdout] 81 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 82 | /     check_feature!(
[INFO] [stdout] 83 | |         core_detect::is_x86_feature_detected!("avx512f"),
[INFO] [stdout] 84 | |         information.avx512f()
[INFO] [stdout] 85 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 86 | /     check_feature!(
[INFO] [stdout] 87 | |         core_detect::is_x86_feature_detected!("avx512cd"),
[INFO] [stdout] 88 | |         information.avx512cd()
[INFO] [stdout] 89 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 90 | /     check_feature!(
[INFO] [stdout] 91 | |         core_detect::is_x86_feature_detected!("avx512er"),
[INFO] [stdout] 92 | |         information.avx512er()
[INFO] [stdout] 93 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]   --> tests/compare_cupid.rs:7:21
[INFO] [stdout]    |
[INFO] [stdout]  7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 94 | /     check_feature!(
[INFO] [stdout] 95 | |         core_detect::is_x86_feature_detected!("avx512pf"),
[INFO] [stdout] 96 | |         information.avx512pf()
[INFO] [stdout] 97 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  98 | /     check_feature!(
[INFO] [stdout]  99 | |         core_detect::is_x86_feature_detected!("avx512bw"),
[INFO] [stdout] 100 | |         information.avx512bw()
[INFO] [stdout] 101 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 102 | /     check_feature!(
[INFO] [stdout] 103 | |         core_detect::is_x86_feature_detected!("avx512dq"),
[INFO] [stdout] 104 | |         information.avx512dq()
[INFO] [stdout] 105 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 106 | /     check_feature!(
[INFO] [stdout] 107 | |         core_detect::is_x86_feature_detected!("avx512vl"),
[INFO] [stdout] 108 | |         information.avx512vl()
[INFO] [stdout] 109 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 110 | /     check_feature!(
[INFO] [stdout] 111 | |         core_detect::is_x86_feature_detected!("avx512ifma"),
[INFO] [stdout] 112 | |         information.avx512_ifma()
[INFO] [stdout] 113 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 114 | /     check_feature!(
[INFO] [stdout] 115 | |         core_detect::is_x86_feature_detected!("avx512vbmi"),
[INFO] [stdout] 116 | |         information.avx512_vbmi()
[INFO] [stdout] 117 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 118 | /     check_feature!(
[INFO] [stdout] 119 | |         core_detect::is_x86_feature_detected!("avx512vpopcntdq"),
[INFO] [stdout] 120 | |         information.avx512_vpopcntdq()
[INFO] [stdout] 121 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 122 | /     check_feature!(
[INFO] [stdout] 123 | |         core_detect::is_x86_feature_detected!("fma"),
[INFO] [stdout] 124 | |         information.fma()
[INFO] [stdout] 125 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 126 | /     check_feature!(
[INFO] [stdout] 127 | |         core_detect::is_x86_feature_detected!("bmi1"),
[INFO] [stdout] 128 | |         information.bmi1()
[INFO] [stdout] 129 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 130 | /     check_feature!(
[INFO] [stdout] 131 | |         core_detect::is_x86_feature_detected!("bmi2"),
[INFO] [stdout] 132 | |         information.bmi2()
[INFO] [stdout] 133 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 134 | /     check_feature!(
[INFO] [stdout] 135 | |         core_detect::is_x86_feature_detected!("popcnt"),
[INFO] [stdout] 136 | |         information.popcnt()
[INFO] [stdout] 137 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 138 | /     check_feature!(
[INFO] [stdout] 139 | |         core_detect::is_x86_feature_detected!("abm"),
[INFO] [stdout] 140 | |         information.lzcnt()
[INFO] [stdout] 141 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 142 | /     check_feature!(
[INFO] [stdout] 143 | |         core_detect::is_x86_feature_detected!("tbm"),
[INFO] [stdout] 144 | |         information.tbm()
[INFO] [stdout] 145 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 146 | /     check_feature!(
[INFO] [stdout] 147 | |         core_detect::is_x86_feature_detected!("lzcnt"),
[INFO] [stdout] 148 | |         information.lzcnt()
[INFO] [stdout] 149 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 150 | /     check_feature!(
[INFO] [stdout] 151 | |         core_detect::is_x86_feature_detected!("xsave"),
[INFO] [stdout] 152 | |         information.xsave()
[INFO] [stdout] 153 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 154 | /     check_feature!(
[INFO] [stdout] 155 | |         core_detect::is_x86_feature_detected!("xsaveopt"),
[INFO] [stdout] 156 | |         information.xsaveopt()
[INFO] [stdout] 157 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 158 | /     check_feature!(
[INFO] [stdout] 159 | |         core_detect::is_x86_feature_detected!("xsavec"),
[INFO] [stdout] 160 | |         information.xsavec_and_xrstor()
[INFO] [stdout] 161 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 162 | /     check_feature!(
[INFO] [stdout] 163 | |         core_detect::is_x86_feature_detected!("xsaves"),
[INFO] [stdout] 164 | |         information.xsaves_xrstors_and_ia32_xss()
[INFO] [stdout] 165 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 166 | /     check_feature!(
[INFO] [stdout] 167 | |         core_detect::is_x86_feature_detected!("cmpxchg16b"),
[INFO] [stdout] 168 | |         information.cmpxchg16b(),
[INFO] [stdout] 169 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 170 | /     check_feature!(
[INFO] [stdout] 171 | |         core_detect::is_x86_feature_detected!("adx"),
[INFO] [stdout] 172 | |         information.adx(),
[INFO] [stdout] 173 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `allow_false_negative`
[INFO] [stdout]    --> tests/compare_cupid.rs:7:21
[INFO] [stdout]     |
[INFO] [stdout]   7 |               if cfg!(allow_false_negative) {
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 174 | /     check_feature!(
[INFO] [stdout] 175 | |         core_detect::is_x86_feature_detected!("rtm"),
[INFO] [stdout] 176 | |         information.rtm(),
[INFO] [stdout] 177 | |     );
[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(allow_false_negative)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_false_negative)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `check_feature` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary transmute
[INFO] [stdout]   --> src/os/x86.rs:97:13
[INFO] [stdout]    |
[INFO] [stdout] 97 |             mem::transmute(ebx),
[INFO] [stdout]    |             --------------^^^^^
[INFO] [stdout]    |             |
[INFO] [stdout]    |             help: replace this with: `u32::to_ne_bytes`
[INFO] [stdout]    |
[INFO] [stdout]    = help: there's also `to_le_bytes` and `to_be_bytes` if you expect a particular byte order
[INFO] [stdout]    = note: `#[warn(unnecessary_transmutes)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary transmute
[INFO] [stdout]   --> src/os/x86.rs:98:13
[INFO] [stdout]    |
[INFO] [stdout] 98 |             mem::transmute(edx),
[INFO] [stdout]    |             --------------^^^^^
[INFO] [stdout]    |             |
[INFO] [stdout]    |             help: replace this with: `u32::to_ne_bytes`
[INFO] [stdout]    |
[INFO] [stdout]    = help: there's also `to_le_bytes` and `to_be_bytes` if you expect a particular byte order
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary transmute
[INFO] [stdout]   --> src/os/x86.rs:99:13
[INFO] [stdout]    |
[INFO] [stdout] 99 |             mem::transmute(ecx),
[INFO] [stdout]    |             --------------^^^^^
[INFO] [stdout]    |             |
[INFO] [stdout]    |             help: replace this with: `u32::to_ne_bytes`
[INFO] [stdout]    |
[INFO] [stdout]    = help: there's also `to_le_bytes` and `to_be_bytes` if you expect a particular byte order
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.27s
[INFO] running `Command { std: "docker" "inspect" "d1e898f162ef5e1114bf592d376bcef4bdae5b44c7d45bb144567080f5615a68", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "d1e898f162ef5e1114bf592d376bcef4bdae5b44c7d45bb144567080f5615a68", kill_on_drop: false }`
[INFO] [stdout] d1e898f162ef5e1114bf592d376bcef4bdae5b44c7d45bb144567080f5615a68
