[INFO] cloning repository https://github.com/creativemindplus/MIRAI [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/creativemindplus/MIRAI" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fcreativemindplus%2FMIRAI", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fcreativemindplus%2FMIRAI'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 576dc3e37421fa390da9dfec122443d36fc817e0 [INFO] testing creativemindplus/MIRAI against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fcreativemindplus%2FMIRAI" "/workspace/builds/worker-4-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-4-tc1/source'... [INFO] [stderr] done. [INFO] removed /workspace/builds/worker-4-tc1/source/rust-toolchain [INFO] started tweaking git repo https://github.com/creativemindplus/MIRAI [INFO] finished tweaking git repo https://github.com/creativemindplus/MIRAI [INFO] tweaked toml for git repo https://github.com/creativemindplus/MIRAI written to /workspace/builds/worker-4-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/creativemindplus/MIRAI on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/creativemindplus/MIRAI already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded shlex v1.1.0 [INFO] [stderr] Downloaded which v3.1.1 [INFO] [stderr] Downloaded proc-macro2 v1.0.32 [INFO] [stderr] Downloaded contracts v0.6.2 [INFO] [stderr] Downloaded darling_macro v0.10.2 [INFO] [stderr] Downloaded archery v0.4.0 [INFO] [stderr] Downloaded env_logger v0.9.0 [INFO] [stderr] Downloaded strsim v0.9.3 [INFO] [stderr] Downloaded darling v0.10.2 [INFO] [stderr] Downloaded darling_core v0.10.2 [INFO] [stderr] Downloaded rpds v0.10.0 [INFO] [stderr] Downloaded indexmap v1.7.0 [INFO] [stderr] Downloaded itertools v0.10.1 [INFO] [stderr] Downloaded serde_json v1.0.71 [INFO] [stderr] Downloaded bindgen v0.58.1 [INFO] [stderr] Downloaded syn v1.0.81 [INFO] [stderr] Downloaded regex v1.5.4 [INFO] [stderr] Downloaded petgraph v0.6.0 [INFO] [stderr] Downloaded serde v1.0.130 [INFO] [stderr] Downloaded crossbeam-epoch v0.9.5 [INFO] [stderr] Downloaded tar v0.4.37 [INFO] [stderr] Downloaded fixedbitset v0.4.0 [INFO] [stderr] Downloaded regex-syntax v0.6.25 [INFO] [stderr] Downloaded serde_derive v1.0.130 [INFO] [stderr] Downloaded crossbeam-utils v0.8.5 [INFO] [stderr] Downloaded cexpr v0.4.0 [INFO] [stderr] Downloaded crc32fast v1.2.1 [INFO] [stderr] Downloaded lock_api v0.4.5 [INFO] [stderr] Downloaded libloading v0.7.2 [INFO] [stderr] Downloaded log-derive v0.4.1 [INFO] [stderr] Downloaded fs2 v0.4.3 [INFO] [stderr] Downloaded smallvec v1.7.0 [INFO] [stderr] Downloaded sled v0.34.7 [INFO] [stderr] Downloaded filetime v0.2.15 [INFO] [stderr] Downloaded redox_syscall v0.2.10 [INFO] [stderr] Downloaded libc v0.2.107 [INFO] [stderr] Downloaded peeking_take_while v0.1.2 [INFO] [stderr] Downloaded walkdir v2.3.2 [INFO] [stderr] Downloaded shellwords v1.1.0 [INFO] [stderr] Downloaded memoffset v0.6.4 [INFO] [stderr] Downloaded clang-sys v1.3.0 [INFO] [stderr] Downloaded z3-sys v0.7.1 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 11be2597cf95ecb83570a1006d7f18d72757d22e0732eea87de37cb4eeadc0d0 [INFO] running `Command { std: "docker" "start" "-a" "11be2597cf95ecb83570a1006d7f18d72757d22e0732eea87de37cb4eeadc0d0", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "11be2597cf95ecb83570a1006d7f18d72757d22e0732eea87de37cb4eeadc0d0", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "11be2597cf95ecb83570a1006d7f18d72757d22e0732eea87de37cb4eeadc0d0", kill_on_drop: false }` [INFO] [stdout] 11be2597cf95ecb83570a1006d7f18d72757d22e0732eea87de37cb4eeadc0d0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] d894cc39fdf98f16c1c959ac874d1738234acc7fedc3de9d5baae342f7bbe9a4 [INFO] running `Command { std: "docker" "start" "-a" "d894cc39fdf98f16c1c959ac874d1738234acc7fedc3de9d5baae342f7bbe9a4", kill_on_drop: false }` [INFO] [stderr] warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"` [INFO] [stderr] note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest [INFO] [stderr] note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest [INFO] [stderr] note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions [INFO] [stderr] Compiling libc v0.2.107 [INFO] [stderr] Compiling proc-macro2 v1.0.32 [INFO] [stderr] Compiling memchr v2.4.1 [INFO] [stderr] Compiling syn v1.0.81 [INFO] [stderr] Compiling log v0.4.14 [INFO] [stderr] Compiling glob v0.3.0 [INFO] [stderr] Compiling cfg-if v1.0.0 [INFO] [stderr] Compiling version_check v0.9.3 [INFO] [stderr] Compiling mirai-annotations v1.12.0 (/opt/rustwide/workdir/annotations) [INFO] [stderr] Compiling unicode-width v0.1.9 [INFO] [stderr] Compiling regex-syntax v0.6.25 [INFO] [stderr] Compiling termcolor v1.1.2 [INFO] [stderr] Compiling bitflags v1.3.2 [INFO] [stderr] Compiling serde_derive v1.0.130 [INFO] [stderr] Compiling bindgen v0.58.1 [INFO] [stderr] Compiling humantime v2.1.0 [INFO] [stderr] Compiling vec_map v0.8.2 [INFO] [stderr] Compiling libloading v0.7.2 [INFO] [stderr] Compiling textwrap v0.11.0 [INFO] [stderr] Compiling ansi_term v0.11.0 [INFO] [stderr] Compiling strsim v0.8.0 [INFO] [stderr] Compiling rustc-hash v1.1.0 [INFO] [stderr] Compiling lazycell v1.3.0 [INFO] [stderr] Compiling peeking_take_while v0.1.2 [INFO] [stderr] Compiling shlex v1.1.0 [INFO] [stderr] Compiling lazy_static v1.4.0 [INFO] [stderr] Compiling aho-corasick v0.7.18 [INFO] [stderr] Compiling serde v1.0.130 [INFO] [stderr] Compiling memoffset v0.6.4 [INFO] [stderr] Compiling crossbeam-utils v0.8.5 [INFO] [stderr] Compiling strsim v0.9.3 [INFO] [stderr] Compiling ident_case v1.0.1 [INFO] [stderr] Compiling parking_lot_core v0.8.5 [INFO] [stderr] Compiling indexmap v1.7.0 [INFO] [stderr] Compiling crossbeam-epoch v0.9.5 [INFO] [stderr] Compiling ryu v1.0.5 [INFO] [stderr] Compiling clang-sys v1.3.0 [INFO] [stderr] Compiling crc32fast v1.2.1 [INFO] [stderr] Compiling smallvec v1.7.0 [INFO] [stderr] Compiling nom v5.1.2 [INFO] [stderr] Compiling lock_api v0.4.5 [INFO] [stderr] Compiling getrandom v0.2.3 [INFO] [stderr] Compiling atty v0.2.14 [INFO] [stderr] Compiling byteorder v1.4.3 [INFO] [stderr] Compiling serde_json v1.0.71 [INFO] [stderr] Compiling which v3.1.1 [INFO] [stderr] Compiling quote v1.0.10 [INFO] [stderr] Compiling clap v2.33.3 [INFO] [stderr] Compiling rand_core v0.6.3 [INFO] [stderr] Compiling static_assertions v1.1.0 [INFO] [stderr] Compiling parking_lot v0.11.2 [INFO] [stderr] Compiling archery v0.4.0 [INFO] [stderr] Compiling regex v1.5.4 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling fxhash v0.2.1 [INFO] [stderr] Compiling fs2 v0.4.3 [INFO] [stderr] Compiling rand v0.8.4 [INFO] [stderr] Compiling xattr v0.2.2 [INFO] [stderr] Compiling filetime v0.2.15 [INFO] [stderr] Compiling mirai v1.0.5 (/opt/rustwide/workdir/checker) [INFO] [stderr] Compiling itoa v0.4.8 [INFO] [stderr] Compiling fixedbitset v0.4.0 [INFO] [stderr] Compiling either v1.6.1 [INFO] [stderr] Compiling remove_dir_all v0.5.3 [INFO] [stderr] Compiling tar v0.4.37 [INFO] [stderr] Compiling sled v0.34.7 [INFO] [stderr] Compiling itertools v0.10.1 [INFO] [stderr] Compiling petgraph v0.6.0 [INFO] [stderr] Compiling cexpr v0.4.0 [INFO] [stderr] Compiling env_logger v0.8.4 [INFO] [stderr] Compiling taint-error v0.1.0 (/opt/rustwide/workdir/examples/taint/taint_error) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/taint/taint_error/src/lib.rs:18:5 [INFO] [stdout] | [INFO] [stdout] 18 | set_model_field!(&result, tainted, true); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `set_model_field` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `set_model_field` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `set_model_field` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/taint/taint_error/src/lib.rs:23:5 [INFO] [stdout] | [INFO] [stdout] 23 | precondition!(!get_model_field!(&f, tainted, false)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling tempfile v3.2.0 [INFO] [stderr] Compiling taint v0.1.0 (/opt/rustwide/workdir/examples/taint) [INFO] [stderr] Compiling mirai-standard-contracts v0.0.1 (/opt/rustwide/workdir/standard_contracts) [INFO] [stderr] Compiling untrustworthy_inputs v0.1.0 (/opt/rustwide/workdir/examples/tag_analysis/untrustworthy_inputs) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:9:13 [INFO] [stdout] | [INFO] [stdout] 9 | #![cfg_attr(mirai, allow(incomplete_features), feature(generic_const_exprs))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:15:7 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:18:7 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:21:7 [INFO] [stdout] | [INFO] [stdout] 21 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:24:7 [INFO] [stdout] | [INFO] [stdout] 24 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:26:11 [INFO] [stdout] | [INFO] [stdout] 26 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:29:7 [INFO] [stdout] | [INFO] [stdout] 29 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:32:7 [INFO] [stdout] | [INFO] [stdout] 32 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:35:7 [INFO] [stdout] | [INFO] [stdout] 35 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:37:11 [INFO] [stdout] | [INFO] [stdout] 37 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:58:13 [INFO] [stdout] | [INFO] [stdout] 58 | add_tag!(&key, Tainted); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:76:17 [INFO] [stdout] | [INFO] [stdout] 76 | add_tag!(&key, Sanitized); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:86:13 [INFO] [stdout] | [INFO] [stdout] 86 | verify!(does_not_have_tag!(&key, crate::Tainted) || has_tag!(&key, crate::Sanitized)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:86:21 [INFO] [stdout] | [INFO] [stdout] 86 | verify!(does_not_have_tag!(&key, crate::Tainted) || has_tag!(&key, crate::Sanitized)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:86:65 [INFO] [stdout] | [INFO] [stdout] 86 | verify!(does_not_have_tag!(&key, crate::Tainted) || has_tag!(&key, crate::Sanitized)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:100:9 [INFO] [stdout] | [INFO] [stdout] 100 | verify!(does_not_have_tag!(&key, crate::Tainted) || has_tag!(&key, crate::Sanitized)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `verify` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:100:17 [INFO] [stdout] | [INFO] [stdout] 100 | verify!(does_not_have_tag!(&key, crate::Tainted) || has_tag!(&key, crate::Sanitized)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `does_not_have_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `does_not_have_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `does_not_have_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:100:61 [INFO] [stdout] | [INFO] [stdout] 100 | verify!(does_not_have_tag!(&key, crate::Tainted) || has_tag!(&key, crate::Sanitized)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> examples/tag_analysis/untrustworthy_inputs/src/lib.rs:41:22 [INFO] [stdout] | [INFO] [stdout] 41 | pub struct PublicKey(u32); [INFO] [stdout] | --------- ^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this struct [INFO] [stdout] | [INFO] [stdout] = help: consider removing this field [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `core_intrinsics` is internal to the compiler or standard library [INFO] [stdout] --> standard_contracts/src/lib.rs:9:12 [INFO] [stdout] | [INFO] [stdout] 9 | #![feature(core_intrinsics)] [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using it is strongly discouraged [INFO] [stdout] = note: `#[warn(internal_features)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `hashmap_internals` is internal to the compiler or standard library [INFO] [stdout] --> standard_contracts/src/lib.rs:12:12 [INFO] [stdout] | [INFO] [stdout] 12 | #![feature(hashmap_internals)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using it is strongly discouraged [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the feature `ptr_internals` is internal to the compiler or standard library [INFO] [stdout] --> standard_contracts/src/lib.rs:15:12 [INFO] [stdout] | [INFO] [stdout] 15 | #![feature(ptr_internals)] [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using it is strongly discouraged [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:16:13 [INFO] [stdout] | [INFO] [stdout] 16 | assume_unreachable!(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume_unreachable` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume_unreachable` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `assume_unreachable` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:38:21 [INFO] [stdout] | [INFO] [stdout] 38 | default_contract!(insert); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | precondition!(edge_idx <= CAPACITY); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:89:9 [INFO] [stdout] | [INFO] [stdout] 89 | default_contract!(format); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:94:13 [INFO] [stdout] | [INFO] [stdout] 94 | assume_unreachable!("capacity overflow"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume_unreachable` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume_unreachable` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume_unreachable` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:126:13 [INFO] [stdout] | [INFO] [stdout] 126 | default_contract!(to_lowercase); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:127:13 [INFO] [stdout] | [INFO] [stdout] 127 | default_contract!(repeat); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:128:13 [INFO] [stdout] | [INFO] [stdout] 128 | default_contract!(replace); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:137:17 [INFO] [stdout] | [INFO] [stdout] 137 | result!() [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:151:13 [INFO] [stdout] | [INFO] [stdout] 151 | default_contract!(drop); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:307:17 [INFO] [stdout] | [INFO] [stdout] 307 | assume_unreachable!("capacity overflow"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume_unreachable` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume_unreachable` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume_unreachable` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:314:13 [INFO] [stdout] | [INFO] [stdout] 314 | default_contract!(new); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:318:13 [INFO] [stdout] | [INFO] [stdout] 318 | default_contract!(next); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:319:13 [INFO] [stdout] | [INFO] [stdout] 319 | default_contract!(size_hint); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:323:13 [INFO] [stdout] | [INFO] [stdout] 323 | default_contract!(next); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:324:13 [INFO] [stdout] | [INFO] [stdout] 324 | default_contract!(size_hint); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:378:13 [INFO] [stdout] | [INFO] [stdout] 378 | ... default_contract!(clone__fn_core_clone_Clone_clone_tuple_2_diem_crypto_ed25519_Ed25519Signature_u8_tuple_1_ref_tuple_2_diem_crypto_ed25519_Ed25519Signature_u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:611:13 [INFO] [stdout] | [INFO] [stdout] 611 | default_contract!(simd_eq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:612:13 [INFO] [stdout] | [INFO] [stdout] 612 | default_contract!(simd_ne); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:613:13 [INFO] [stdout] | [INFO] [stdout] 613 | default_contract!(simd_lt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:614:13 [INFO] [stdout] | [INFO] [stdout] 614 | default_contract!(simd_le); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:615:13 [INFO] [stdout] | [INFO] [stdout] 615 | default_contract!(simd_gt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:616:13 [INFO] [stdout] | [INFO] [stdout] 616 | default_contract!(simd_ge); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:617:13 [INFO] [stdout] | [INFO] [stdout] 617 | default_contract!(simd_shuffle2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:618:13 [INFO] [stdout] | [INFO] [stdout] 618 | default_contract!(simd_shuffle4); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:619:13 [INFO] [stdout] | [INFO] [stdout] 619 | default_contract!(simd_shuffle8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling timing_channels v0.1.0 (/opt/rustwide/workdir/examples/tag_analysis/timing_channels) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:620:13 [INFO] [stdout] | [INFO] [stdout] 620 | default_contract!(simd_shuffle16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:621:13 [INFO] [stdout] | [INFO] [stdout] 621 | default_contract!(simd_shuffle32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling verification_status v0.1.0 (/opt/rustwide/workdir/examples/tag_analysis/verification_status) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:622:13 [INFO] [stdout] | [INFO] [stdout] 622 | default_contract!(simd_shuffle64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:623:13 [INFO] [stdout] | [INFO] [stdout] 623 | default_contract!(simd_shuffle128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:624:13 [INFO] [stdout] | [INFO] [stdout] 624 | default_contract!(simd_insert); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:625:13 [INFO] [stdout] | [INFO] [stdout] 625 | default_contract!(simd_extract); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:627:13 [INFO] [stdout] | [INFO] [stdout] 627 | default_contract!(simd_bitmask); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:628:13 [INFO] [stdout] | [INFO] [stdout] 628 | default_contract!(simd_cast); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:629:13 [INFO] [stdout] | [INFO] [stdout] 629 | default_contract!(simd_add); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:630:13 [INFO] [stdout] | [INFO] [stdout] 630 | default_contract!(simd_sub); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:631:13 [INFO] [stdout] | [INFO] [stdout] 631 | default_contract!(simd_mul); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:632:13 [INFO] [stdout] | [INFO] [stdout] 632 | default_contract!(simd_div); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:633:13 [INFO] [stdout] | [INFO] [stdout] 633 | default_contract!(simd_shl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:634:13 [INFO] [stdout] | [INFO] [stdout] 634 | default_contract!(simd_shr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:635:13 [INFO] [stdout] | [INFO] [stdout] 635 | default_contract!(simd_and); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:636:13 [INFO] [stdout] | [INFO] [stdout] 636 | default_contract!(simd_or); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:637:13 [INFO] [stdout] | [INFO] [stdout] 637 | default_contract!(simd_xor); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:638:13 [INFO] [stdout] | [INFO] [stdout] 638 | default_contract!(simd_saturating_add); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:639:13 [INFO] [stdout] | [INFO] [stdout] 639 | default_contract!(simd_saturating_sub); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:640:13 [INFO] [stdout] | [INFO] [stdout] 640 | default_contract!(simd_gather); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:643:13 [INFO] [stdout] | [INFO] [stdout] 643 | default_contract!(simd_reduce_add_unordered); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:644:13 [INFO] [stdout] | [INFO] [stdout] 644 | default_contract!(simd_reduce_mul_unordered); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:645:13 [INFO] [stdout] | [INFO] [stdout] 645 | default_contract!(simd_reduce_add_ordered); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:646:13 [INFO] [stdout] | [INFO] [stdout] 646 | default_contract!(simd_reduce_mul_ordered); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:647:13 [INFO] [stdout] | [INFO] [stdout] 647 | default_contract!(simd_reduce_min); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:648:13 [INFO] [stdout] | [INFO] [stdout] 648 | default_contract!(simd_reduce_max); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:649:13 [INFO] [stdout] | [INFO] [stdout] 649 | default_contract!(simd_reduce_min_nanless); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:650:13 [INFO] [stdout] | [INFO] [stdout] 650 | default_contract!(simd_reduce_max_nanless); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:651:13 [INFO] [stdout] | [INFO] [stdout] 651 | default_contract!(simd_reduce_and); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:652:13 [INFO] [stdout] | [INFO] [stdout] 652 | default_contract!(simd_reduce_or); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:653:13 [INFO] [stdout] | [INFO] [stdout] 653 | default_contract!(simd_reduce_xor); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:654:13 [INFO] [stdout] | [INFO] [stdout] 654 | default_contract!(simd_reduce_all); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:655:13 [INFO] [stdout] | [INFO] [stdout] 655 | default_contract!(simd_reduce_any); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:656:13 [INFO] [stdout] | [INFO] [stdout] 656 | default_contract!(simd_select); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:657:13 [INFO] [stdout] | [INFO] [stdout] 657 | default_contract!(simd_select_bitmask); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:658:13 [INFO] [stdout] | [INFO] [stdout] 658 | default_contract!(simd_fmin); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:659:13 [INFO] [stdout] | [INFO] [stdout] 659 | default_contract!(simd_fmax); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:660:13 [INFO] [stdout] | [INFO] [stdout] 660 | default_contract!(simd_fsqrt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:661:13 [INFO] [stdout] | [INFO] [stdout] 661 | default_contract!(simd_fsin); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:662:13 [INFO] [stdout] | [INFO] [stdout] 662 | default_contract!(simd_fcos); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:663:13 [INFO] [stdout] | [INFO] [stdout] 663 | default_contract!(simd_fabs); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:664:13 [INFO] [stdout] | [INFO] [stdout] 664 | default_contract!(simd_floor); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:665:13 [INFO] [stdout] | [INFO] [stdout] 665 | default_contract!(simd_ceil); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:666:13 [INFO] [stdout] | [INFO] [stdout] 666 | default_contract!(simd_fexp); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:667:13 [INFO] [stdout] | [INFO] [stdout] 667 | default_contract!(simd_fexp2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:668:13 [INFO] [stdout] | [INFO] [stdout] 668 | default_contract!(simd_flog10); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:669:13 [INFO] [stdout] | [INFO] [stdout] 669 | default_contract!(simd_flog2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:670:13 [INFO] [stdout] | [INFO] [stdout] 670 | default_contract!(simd_flog); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:673:13 [INFO] [stdout] | [INFO] [stdout] 673 | default_contract!(simd_fma); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:699:17 [INFO] [stdout] | [INFO] [stdout] 699 | default_contract!(addsubpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:700:17 [INFO] [stdout] | [INFO] [stdout] 700 | default_contract!(addsubps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:701:17 [INFO] [stdout] | [INFO] [stdout] 701 | default_contract!(roundpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:702:17 [INFO] [stdout] | [INFO] [stdout] 702 | default_contract!(roundps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:703:17 [INFO] [stdout] | [INFO] [stdout] 703 | default_contract!(sqrtps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:704:17 [INFO] [stdout] | [INFO] [stdout] 704 | default_contract!(vblendvpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:705:17 [INFO] [stdout] | [INFO] [stdout] 705 | default_contract!(vblendvps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:706:17 [INFO] [stdout] | [INFO] [stdout] 706 | default_contract!(vdpps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:707:17 [INFO] [stdout] | [INFO] [stdout] 707 | default_contract!(vhaddpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:708:17 [INFO] [stdout] | [INFO] [stdout] 708 | default_contract!(vhaddps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:709:17 [INFO] [stdout] | [INFO] [stdout] 709 | default_contract!(vhsubpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:710:17 [INFO] [stdout] | [INFO] [stdout] 710 | default_contract!(vhsubps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:711:17 [INFO] [stdout] | [INFO] [stdout] 711 | default_contract!(vcmppd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:712:17 [INFO] [stdout] | [INFO] [stdout] 712 | default_contract!(vcmppd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:713:17 [INFO] [stdout] | [INFO] [stdout] 713 | default_contract!(vcmpps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:714:17 [INFO] [stdout] | [INFO] [stdout] 714 | default_contract!(vcmpps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:715:17 [INFO] [stdout] | [INFO] [stdout] 715 | default_contract!(vcmpsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:716:17 [INFO] [stdout] | [INFO] [stdout] 716 | default_contract!(vcmpss); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:717:17 [INFO] [stdout] | [INFO] [stdout] 717 | default_contract!(vcvtdq2ps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:718:17 [INFO] [stdout] | [INFO] [stdout] 718 | default_contract!(vcvtpd2ps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:719:17 [INFO] [stdout] | [INFO] [stdout] 719 | default_contract!(vcvtps2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:720:17 [INFO] [stdout] | [INFO] [stdout] 720 | default_contract!(vcvttpd2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:721:17 [INFO] [stdout] | [INFO] [stdout] 721 | default_contract!(vcvtpd2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:722:17 [INFO] [stdout] | [INFO] [stdout] 722 | default_contract!(vcvttps2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:723:17 [INFO] [stdout] | [INFO] [stdout] 723 | default_contract!(vzeroall); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:724:17 [INFO] [stdout] | [INFO] [stdout] 724 | default_contract!(vzeroupper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:725:17 [INFO] [stdout] | [INFO] [stdout] 725 | default_contract!(vpermilps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:726:17 [INFO] [stdout] | [INFO] [stdout] 726 | default_contract!(vpermilps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:727:17 [INFO] [stdout] | [INFO] [stdout] 727 | default_contract!(vpermilpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:728:17 [INFO] [stdout] | [INFO] [stdout] 728 | default_contract!(vpermilpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:729:17 [INFO] [stdout] | [INFO] [stdout] 729 | default_contract!(vperm2f128ps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:730:17 [INFO] [stdout] | [INFO] [stdout] 730 | default_contract!(vperm2f128pd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:731:17 [INFO] [stdout] | [INFO] [stdout] 731 | default_contract!(vperm2f128si256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:732:17 [INFO] [stdout] | [INFO] [stdout] 732 | default_contract!(vbroadcastf128ps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:733:17 [INFO] [stdout] | [INFO] [stdout] 733 | default_contract!(vbroadcastf128pd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:749:17 [INFO] [stdout] | [INFO] [stdout] 749 | default_contract!(maskloadpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:750:17 [INFO] [stdout] | [INFO] [stdout] 750 | default_contract!(maskstorepd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:751:17 [INFO] [stdout] | [INFO] [stdout] 751 | default_contract!(maskloadpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:752:17 [INFO] [stdout] | [INFO] [stdout] 752 | default_contract!(maskstorepd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:753:17 [INFO] [stdout] | [INFO] [stdout] 753 | default_contract!(maskloadps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:754:17 [INFO] [stdout] | [INFO] [stdout] 754 | default_contract!(maskstoreps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:755:17 [INFO] [stdout] | [INFO] [stdout] 755 | default_contract!(maskloadps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:759:17 [INFO] [stdout] | [INFO] [stdout] 759 | default_contract!(vlddqu); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:760:17 [INFO] [stdout] | [INFO] [stdout] 760 | default_contract!(vrcpps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:761:17 [INFO] [stdout] | [INFO] [stdout] 761 | default_contract!(vrsqrtps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:762:17 [INFO] [stdout] | [INFO] [stdout] 762 | default_contract!(ptestz256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:763:17 [INFO] [stdout] | [INFO] [stdout] 763 | default_contract!(ptestc256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:764:17 [INFO] [stdout] | [INFO] [stdout] 764 | default_contract!(ptestnzc256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:765:17 [INFO] [stdout] | [INFO] [stdout] 765 | default_contract!(vtestzpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:766:17 [INFO] [stdout] | [INFO] [stdout] 766 | default_contract!(vtestcpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:767:17 [INFO] [stdout] | [INFO] [stdout] 767 | default_contract!(vtestnzcpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:768:17 [INFO] [stdout] | [INFO] [stdout] 768 | default_contract!(vtestzpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:769:17 [INFO] [stdout] | [INFO] [stdout] 769 | default_contract!(vtestcpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:770:17 [INFO] [stdout] | [INFO] [stdout] 770 | default_contract!(vtestnzcpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:771:17 [INFO] [stdout] | [INFO] [stdout] 771 | default_contract!(vtestzps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:772:17 [INFO] [stdout] | [INFO] [stdout] 772 | default_contract!(vtestcps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:773:17 [INFO] [stdout] | [INFO] [stdout] 773 | default_contract!(vtestnzcps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:774:17 [INFO] [stdout] | [INFO] [stdout] 774 | default_contract!(vtestzps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:775:17 [INFO] [stdout] | [INFO] [stdout] 775 | default_contract!(vtestcps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:776:17 [INFO] [stdout] | [INFO] [stdout] 776 | default_contract!(vtestnzcps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:777:17 [INFO] [stdout] | [INFO] [stdout] 777 | default_contract!(movmskpd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:778:17 [INFO] [stdout] | [INFO] [stdout] 778 | default_contract!(movmskps256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:802:17 [INFO] [stdout] | [INFO] [stdout] 802 | default_contract!(pabsb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:803:17 [INFO] [stdout] | [INFO] [stdout] 803 | default_contract!(pabsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:804:17 [INFO] [stdout] | [INFO] [stdout] 804 | default_contract!(pabsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:805:17 [INFO] [stdout] | [INFO] [stdout] 805 | default_contract!(pavgb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:806:17 [INFO] [stdout] | [INFO] [stdout] 806 | default_contract!(pavgw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:807:17 [INFO] [stdout] | [INFO] [stdout] 807 | default_contract!(pblendvb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:808:17 [INFO] [stdout] | [INFO] [stdout] 808 | default_contract!(phaddw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:809:17 [INFO] [stdout] | [INFO] [stdout] 809 | default_contract!(phaddd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:810:17 [INFO] [stdout] | [INFO] [stdout] 810 | default_contract!(phaddsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:811:17 [INFO] [stdout] | [INFO] [stdout] 811 | default_contract!(phsubw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:9:13 [INFO] [stdout] | [INFO] [stdout] 9 | #![cfg_attr(mirai, allow(incomplete_features), feature(generic_const_exprs))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:812:17 [INFO] [stdout] | [INFO] [stdout] 812 | default_contract!(phsubd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:14:7 [INFO] [stdout] | [INFO] [stdout] 14 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:17:7 [INFO] [stdout] | [INFO] [stdout] 17 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:20:7 [INFO] [stdout] | [INFO] [stdout] 20 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:23:7 [INFO] [stdout] | [INFO] [stdout] 23 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:813:17 [INFO] [stdout] | [INFO] [stdout] 813 | default_contract!(phsubsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:25:11 [INFO] [stdout] | [INFO] [stdout] 25 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:42:13 [INFO] [stdout] | [INFO] [stdout] 42 | add_tag!(self, Verified); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `add_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `add_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `add_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:814:17 [INFO] [stdout] | [INFO] [stdout] 814 | default_contract!(pmaddwd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:66:9 [INFO] [stdout] | [INFO] [stdout] 66 | precondition!(has_tag!(&vote_msg, crate::Verified)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:815:17 [INFO] [stdout] | [INFO] [stdout] 815 | default_contract!(pmaddubsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/verification_status/src/lib.rs:66:23 [INFO] [stdout] | [INFO] [stdout] 66 | precondition!(has_tag!(&vote_msg, crate::Verified)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:816:17 [INFO] [stdout] | [INFO] [stdout] 816 | default_contract!(maskloadd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:817:17 [INFO] [stdout] | [INFO] [stdout] 817 | default_contract!(maskloadd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:818:17 [INFO] [stdout] | [INFO] [stdout] 818 | default_contract!(maskloadq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:819:17 [INFO] [stdout] | [INFO] [stdout] 819 | default_contract!(maskloadq256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:832:17 [INFO] [stdout] | [INFO] [stdout] 832 | default_contract!(pmaxsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:833:17 [INFO] [stdout] | [INFO] [stdout] 833 | default_contract!(pmaxsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:834:17 [INFO] [stdout] | [INFO] [stdout] 834 | default_contract!(pmaxsb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:835:17 [INFO] [stdout] | [INFO] [stdout] 835 | default_contract!(pmaxuw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:836:17 [INFO] [stdout] | [INFO] [stdout] 836 | default_contract!(pmaxud); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:837:17 [INFO] [stdout] | [INFO] [stdout] 837 | default_contract!(pmaxub); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:838:17 [INFO] [stdout] | [INFO] [stdout] 838 | default_contract!(pminsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:839:17 [INFO] [stdout] | [INFO] [stdout] 839 | default_contract!(pminsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:840:17 [INFO] [stdout] | [INFO] [stdout] 840 | default_contract!(pminsb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:841:17 [INFO] [stdout] | [INFO] [stdout] 841 | default_contract!(pminuw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:842:17 [INFO] [stdout] | [INFO] [stdout] 842 | default_contract!(pminud); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:843:17 [INFO] [stdout] | [INFO] [stdout] 843 | default_contract!(pminub); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:844:17 [INFO] [stdout] | [INFO] [stdout] 844 | default_contract!(pmovmskb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:845:17 [INFO] [stdout] | [INFO] [stdout] 845 | default_contract!(mpsadbw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:846:17 [INFO] [stdout] | [INFO] [stdout] 846 | default_contract!(pmulhuw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:847:17 [INFO] [stdout] | [INFO] [stdout] 847 | default_contract!(pmulhw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:848:17 [INFO] [stdout] | [INFO] [stdout] 848 | default_contract!(pmuldq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:849:17 [INFO] [stdout] | [INFO] [stdout] 849 | default_contract!(pmuludq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:850:17 [INFO] [stdout] | [INFO] [stdout] 850 | default_contract!(pmulhrsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:851:17 [INFO] [stdout] | [INFO] [stdout] 851 | default_contract!(packsswb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:852:17 [INFO] [stdout] | [INFO] [stdout] 852 | default_contract!(packssdw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:853:17 [INFO] [stdout] | [INFO] [stdout] 853 | default_contract!(packuswb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:854:17 [INFO] [stdout] | [INFO] [stdout] 854 | default_contract!(packusdw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:855:17 [INFO] [stdout] | [INFO] [stdout] 855 | default_contract!(psadbw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:856:17 [INFO] [stdout] | [INFO] [stdout] 856 | default_contract!(psignb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:857:17 [INFO] [stdout] | [INFO] [stdout] 857 | default_contract!(psignw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:858:17 [INFO] [stdout] | [INFO] [stdout] 858 | default_contract!(psignd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:859:17 [INFO] [stdout] | [INFO] [stdout] 859 | default_contract!(psllw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:860:17 [INFO] [stdout] | [INFO] [stdout] 860 | default_contract!(pslld); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:861:17 [INFO] [stdout] | [INFO] [stdout] 861 | default_contract!(psllq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:862:17 [INFO] [stdout] | [INFO] [stdout] 862 | default_contract!(pslliw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:863:17 [INFO] [stdout] | [INFO] [stdout] 863 | default_contract!(psllid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:864:17 [INFO] [stdout] | [INFO] [stdout] 864 | default_contract!(pslliq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:865:17 [INFO] [stdout] | [INFO] [stdout] 865 | default_contract!(psllvd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:866:17 [INFO] [stdout] | [INFO] [stdout] 866 | default_contract!(psllvd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:867:17 [INFO] [stdout] | [INFO] [stdout] 867 | default_contract!(psllvq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:868:17 [INFO] [stdout] | [INFO] [stdout] 868 | default_contract!(psllvq256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:869:17 [INFO] [stdout] | [INFO] [stdout] 869 | default_contract!(psraw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:870:17 [INFO] [stdout] | [INFO] [stdout] 870 | default_contract!(psrad); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:871:17 [INFO] [stdout] | [INFO] [stdout] 871 | default_contract!(psraiw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:872:17 [INFO] [stdout] | [INFO] [stdout] 872 | default_contract!(psraid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:873:17 [INFO] [stdout] | [INFO] [stdout] 873 | default_contract!(psravd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:874:17 [INFO] [stdout] | [INFO] [stdout] 874 | default_contract!(psravd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:875:17 [INFO] [stdout] | [INFO] [stdout] 875 | default_contract!(psrlw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:876:17 [INFO] [stdout] | [INFO] [stdout] 876 | default_contract!(psrld); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:877:17 [INFO] [stdout] | [INFO] [stdout] 877 | default_contract!(psrlq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:878:17 [INFO] [stdout] | [INFO] [stdout] 878 | default_contract!(psrliw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:879:17 [INFO] [stdout] | [INFO] [stdout] 879 | default_contract!(psrlid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:880:17 [INFO] [stdout] | [INFO] [stdout] 880 | default_contract!(psrliq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:881:17 [INFO] [stdout] | [INFO] [stdout] 881 | default_contract!(psrlvd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:882:17 [INFO] [stdout] | [INFO] [stdout] 882 | default_contract!(psrlvd256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:883:17 [INFO] [stdout] | [INFO] [stdout] 883 | default_contract!(psrlvq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:884:17 [INFO] [stdout] | [INFO] [stdout] 884 | default_contract!(psrlvq256); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:885:17 [INFO] [stdout] | [INFO] [stdout] 885 | default_contract!(pshufb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:886:17 [INFO] [stdout] | [INFO] [stdout] 886 | default_contract!(permd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:887:17 [INFO] [stdout] | [INFO] [stdout] 887 | default_contract!(permps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:888:17 [INFO] [stdout] | [INFO] [stdout] 888 | default_contract!(vperm2i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:889:17 [INFO] [stdout] | [INFO] [stdout] 889 | default_contract!(pgatherdd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:890:17 [INFO] [stdout] | [INFO] [stdout] 890 | default_contract!(vpgatherdd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:891:17 [INFO] [stdout] | [INFO] [stdout] 891 | default_contract!(pgatherdq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:892:17 [INFO] [stdout] | [INFO] [stdout] 892 | default_contract!(vpgatherdq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:893:17 [INFO] [stdout] | [INFO] [stdout] 893 | default_contract!(pgatherqd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:894:17 [INFO] [stdout] | [INFO] [stdout] 894 | default_contract!(vpgatherqd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:895:17 [INFO] [stdout] | [INFO] [stdout] 895 | default_contract!(pgatherqq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:896:17 [INFO] [stdout] | [INFO] [stdout] 896 | default_contract!(vpgatherqq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:897:17 [INFO] [stdout] | [INFO] [stdout] 897 | default_contract!(pgatherdpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:898:17 [INFO] [stdout] | [INFO] [stdout] 898 | default_contract!(vpgatherdpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:899:17 [INFO] [stdout] | [INFO] [stdout] 899 | default_contract!(pgatherqpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:10:13 [INFO] [stdout] | [INFO] [stdout] 10 | #![cfg_attr(mirai, allow(incomplete_features), feature(generic_const_exprs))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:900:17 [INFO] [stdout] | [INFO] [stdout] 900 | default_contract!(vpgatherqpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:15:7 [INFO] [stdout] | [INFO] [stdout] 15 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:901:17 [INFO] [stdout] | [INFO] [stdout] 901 | default_contract!(pgatherdps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:18:7 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:902:17 [INFO] [stdout] | [INFO] [stdout] 902 | default_contract!(vpgatherdps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:21:7 [INFO] [stdout] | [INFO] [stdout] 21 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:903:17 [INFO] [stdout] | [INFO] [stdout] 903 | default_contract!(pgatherqps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:31:7 [INFO] [stdout] | [INFO] [stdout] 31 | #[cfg(mirai)] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:904:17 [INFO] [stdout] | [INFO] [stdout] 904 | default_contract!(vpgatherqps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:33:11 [INFO] [stdout] | [INFO] [stdout] 33 | #[cfg(not(mirai))] [INFO] [stdout] | ^^^^^ help: there is a config with a similar name: `miri` [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(mirai)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(mirai)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:905:17 [INFO] [stdout] | [INFO] [stdout] 905 | default_contract!(vpslldq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:41:9 [INFO] [stdout] | [INFO] [stdout] 41 | precondition!(has_tag!(secret, crate::SecretTaint)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:906:17 [INFO] [stdout] | [INFO] [stdout] 906 | default_contract!(vpsrldq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:41:23 [INFO] [stdout] | [INFO] [stdout] 41 | precondition!(has_tag!(secret, crate::SecretTaint)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:935:17 [INFO] [stdout] | [INFO] [stdout] 935 | default_contract!(pavgb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:58:9 [INFO] [stdout] | [INFO] [stdout] 58 | precondition!(has_tag!(secret, crate::SecretTaint)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:936:17 [INFO] [stdout] | [INFO] [stdout] 936 | default_contract!(pavgw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:937:17 [INFO] [stdout] | [INFO] [stdout] 937 | default_contract!(pmaddwd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:938:17 [INFO] [stdout] | [INFO] [stdout] 938 | default_contract!(pmaxsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:939:17 [INFO] [stdout] | [INFO] [stdout] 939 | default_contract!(pmaxub); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:940:17 [INFO] [stdout] | [INFO] [stdout] 940 | default_contract!(pminsw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:941:17 [INFO] [stdout] | [INFO] [stdout] 941 | default_contract!(pminub); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:942:17 [INFO] [stdout] | [INFO] [stdout] 942 | default_contract!(pmulhw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:943:17 [INFO] [stdout] | [INFO] [stdout] 943 | default_contract!(pmulhuw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:944:17 [INFO] [stdout] | [INFO] [stdout] 944 | default_contract!(pmuludq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:945:17 [INFO] [stdout] | [INFO] [stdout] 945 | default_contract!(psadbw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:946:17 [INFO] [stdout] | [INFO] [stdout] 946 | default_contract!(pslliw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:947:17 [INFO] [stdout] | [INFO] [stdout] 947 | default_contract!(psllw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:948:17 [INFO] [stdout] | [INFO] [stdout] 948 | default_contract!(psllid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:949:17 [INFO] [stdout] | [INFO] [stdout] 949 | default_contract!(pslld); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:950:17 [INFO] [stdout] | [INFO] [stdout] 950 | default_contract!(pslliq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:951:17 [INFO] [stdout] | [INFO] [stdout] 951 | default_contract!(psllq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:952:17 [INFO] [stdout] | [INFO] [stdout] 952 | default_contract!(psraiw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:953:17 [INFO] [stdout] | [INFO] [stdout] 953 | default_contract!(psraw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:954:17 [INFO] [stdout] | [INFO] [stdout] 954 | default_contract!(psraid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:955:17 [INFO] [stdout] | [INFO] [stdout] 955 | default_contract!(psrad); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:956:17 [INFO] [stdout] | [INFO] [stdout] 956 | default_contract!(psrliw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:957:17 [INFO] [stdout] | [INFO] [stdout] 957 | default_contract!(psrlw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:958:17 [INFO] [stdout] | [INFO] [stdout] 958 | default_contract!(psrlid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:959:17 [INFO] [stdout] | [INFO] [stdout] 959 | default_contract!(psrld); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:960:17 [INFO] [stdout] | [INFO] [stdout] 960 | default_contract!(psrliq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:961:17 [INFO] [stdout] | [INFO] [stdout] 961 | default_contract!(psrlq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:962:17 [INFO] [stdout] | [INFO] [stdout] 962 | default_contract!(cvtdq2ps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:963:17 [INFO] [stdout] | [INFO] [stdout] 963 | default_contract!(cvtps2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:967:17 [INFO] [stdout] | [INFO] [stdout] 967 | default_contract!(packsswb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:968:17 [INFO] [stdout] | [INFO] [stdout] 968 | default_contract!(packssdw); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:969:17 [INFO] [stdout] | [INFO] [stdout] 969 | default_contract!(packuswb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:970:17 [INFO] [stdout] | [INFO] [stdout] 970 | default_contract!(pmovmskb); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:971:17 [INFO] [stdout] | [INFO] [stdout] 971 | default_contract!(maxsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:972:17 [INFO] [stdout] | [INFO] [stdout] 972 | default_contract!(maxpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:973:17 [INFO] [stdout] | [INFO] [stdout] 973 | default_contract!(minsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:974:17 [INFO] [stdout] | [INFO] [stdout] 974 | default_contract!(minpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:975:17 [INFO] [stdout] | [INFO] [stdout] 975 | default_contract!(sqrtsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:976:17 [INFO] [stdout] | [INFO] [stdout] 976 | default_contract!(sqrtpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:977:17 [INFO] [stdout] | [INFO] [stdout] 977 | default_contract!(cmpsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:978:17 [INFO] [stdout] | [INFO] [stdout] 978 | default_contract!(cmppd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:979:17 [INFO] [stdout] | [INFO] [stdout] 979 | default_contract!(comieqsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:980:17 [INFO] [stdout] | [INFO] [stdout] 980 | default_contract!(comiltsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:981:17 [INFO] [stdout] | [INFO] [stdout] 981 | default_contract!(comilesd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:982:17 [INFO] [stdout] | [INFO] [stdout] 982 | default_contract!(comigtsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:983:17 [INFO] [stdout] | [INFO] [stdout] 983 | default_contract!(comigesd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:984:17 [INFO] [stdout] | [INFO] [stdout] 984 | default_contract!(comineqsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:985:17 [INFO] [stdout] | [INFO] [stdout] 985 | default_contract!(ucomieqsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:986:17 [INFO] [stdout] | [INFO] [stdout] 986 | default_contract!(ucomiltsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:987:17 [INFO] [stdout] | [INFO] [stdout] 987 | default_contract!(ucomilesd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:988:17 [INFO] [stdout] | [INFO] [stdout] 988 | default_contract!(ucomigtsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:989:17 [INFO] [stdout] | [INFO] [stdout] 989 | default_contract!(ucomigesd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:990:17 [INFO] [stdout] | [INFO] [stdout] 990 | default_contract!(ucomineqsd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:991:17 [INFO] [stdout] | [INFO] [stdout] 991 | default_contract!(movmskpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:992:17 [INFO] [stdout] | [INFO] [stdout] 992 | default_contract!(cvtpd2ps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:993:17 [INFO] [stdout] | [INFO] [stdout] 993 | default_contract!(cvtps2pd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:994:17 [INFO] [stdout] | [INFO] [stdout] 994 | default_contract!(cvtpd2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:995:17 [INFO] [stdout] | [INFO] [stdout] 995 | default_contract!(cvtsd2si); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:996:17 [INFO] [stdout] | [INFO] [stdout] 996 | default_contract!(cvtsd2ss); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:997:17 [INFO] [stdout] | [INFO] [stdout] 997 | default_contract!(cvtss2sd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:998:17 [INFO] [stdout] | [INFO] [stdout] 998 | default_contract!(cvttpd2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:999:17 [INFO] [stdout] | [INFO] [stdout] 999 | default_contract!(cvttsd2si); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1000:17 [INFO] [stdout] | [INFO] [stdout] 1000 | default_contract!(cvttps2dq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> examples/tag_analysis/timing_channels/src/lib.rs:58:23 [INFO] [stdout] | [INFO] [stdout] 58 | precondition!(has_tag!(secret, crate::SecretTaint)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `has_tag` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `has_tag` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `has_tag` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1035:17 [INFO] [stdout] | [INFO] [stdout] 1035 | default_contract!(addsubps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1036:17 [INFO] [stdout] | [INFO] [stdout] 1036 | default_contract!(addsubpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1037:17 [INFO] [stdout] | [INFO] [stdout] 1037 | default_contract!(haddpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1038:17 [INFO] [stdout] | [INFO] [stdout] 1038 | default_contract!(haddps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1039:17 [INFO] [stdout] | [INFO] [stdout] 1039 | default_contract!(hsubpd); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1040:17 [INFO] [stdout] | [INFO] [stdout] 1040 | default_contract!(hsubps); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1041:17 [INFO] [stdout] | [INFO] [stdout] 1041 | default_contract!(lddqu); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1062:17 [INFO] [stdout] | [INFO] [stdout] 1062 | default_contract!(pabsb128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1063:17 [INFO] [stdout] | [INFO] [stdout] 1063 | default_contract!(pabsw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1064:17 [INFO] [stdout] | [INFO] [stdout] 1064 | default_contract!(pabsd128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1065:17 [INFO] [stdout] | [INFO] [stdout] 1065 | default_contract!(pshufb128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1066:17 [INFO] [stdout] | [INFO] [stdout] 1066 | default_contract!(phaddw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1067:17 [INFO] [stdout] | [INFO] [stdout] 1067 | default_contract!(phaddsw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1068:17 [INFO] [stdout] | [INFO] [stdout] 1068 | default_contract!(phaddd128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1069:17 [INFO] [stdout] | [INFO] [stdout] 1069 | default_contract!(phsubw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1070:17 [INFO] [stdout] | [INFO] [stdout] 1070 | default_contract!(phsubsw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1071:17 [INFO] [stdout] | [INFO] [stdout] 1071 | default_contract!(phsubd128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1072:17 [INFO] [stdout] | [INFO] [stdout] 1072 | default_contract!(pmaddubsw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1073:17 [INFO] [stdout] | [INFO] [stdout] 1073 | default_contract!(pmulhrsw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1074:17 [INFO] [stdout] | [INFO] [stdout] 1074 | default_contract!(psignb128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1075:17 [INFO] [stdout] | [INFO] [stdout] 1075 | default_contract!(psignw128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1076:17 [INFO] [stdout] | [INFO] [stdout] 1076 | default_contract!(psignd128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1082:17 [INFO] [stdout] | [INFO] [stdout] 1082 | default_contract!(llvm_addcarry_u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1083:17 [INFO] [stdout] | [INFO] [stdout] 1083 | default_contract!(llvm_subborrow_u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1090:13 [INFO] [stdout] | [INFO] [stdout] 1090 | default_contract!(default); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1113:17 [INFO] [stdout] | [INFO] [stdout] 1113 | default_contract!(field); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1114:17 [INFO] [stdout] | [INFO] [stdout] 1114 | default_contract!(finish); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1118:17 [INFO] [stdout] | [INFO] [stdout] 1118 | default_contract!(field); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1119:17 [INFO] [stdout] | [INFO] [stdout] 1119 | default_contract!(finish); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1125:17 [INFO] [stdout] | [INFO] [stdout] 1125 | default_contract!(fmt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1130:13 [INFO] [stdout] | [INFO] [stdout] 1130 | default_contract!(fmt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1134:13 [INFO] [stdout] | [INFO] [stdout] 1134 | default_contract!(debug_struct); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1135:13 [INFO] [stdout] | [INFO] [stdout] 1135 | default_contract!(debug_tuple); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1136:13 [INFO] [stdout] | [INFO] [stdout] 1136 | default_contract!(new); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1137:13 [INFO] [stdout] | [INFO] [stdout] 1137 | default_contract!(write_fmt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1138:13 [INFO] [stdout] | [INFO] [stdout] 1138 | default_contract!(write_str); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1142:13 [INFO] [stdout] | [INFO] [stdout] 1142 | default_contract!(fmt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1148:21 [INFO] [stdout] | [INFO] [stdout] 1148 | default_contract!(fmt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1160:9 [INFO] [stdout] | [INFO] [stdout] 1160 | default_contract!(write); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1185:9 [INFO] [stdout] | [INFO] [stdout] 1185 | atomic_cxchg!(atomic_cxchg__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1186:9 [INFO] [stdout] | [INFO] [stdout] 1186 | atomic_cxchg!(atomic_cxchg__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1187:9 [INFO] [stdout] | [INFO] [stdout] 1187 | atomic_cxchg!(atomic_cxchg__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1188:9 [INFO] [stdout] | [INFO] [stdout] 1188 | atomic_cxchg!(atomic_cxchg__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1189:9 [INFO] [stdout] | [INFO] [stdout] 1189 | atomic_cxchg!(atomic_cxchg__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1190:9 [INFO] [stdout] | [INFO] [stdout] 1190 | atomic_cxchg!(atomic_cxchg__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1191:9 [INFO] [stdout] | [INFO] [stdout] 1191 | atomic_cxchg!(atomic_cxchg__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1192:9 [INFO] [stdout] | [INFO] [stdout] 1192 | atomic_cxchg!(atomic_cxchg__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1193:9 [INFO] [stdout] | [INFO] [stdout] 1193 | atomic_cxchg!(atomic_cxchg__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1194:9 [INFO] [stdout] | [INFO] [stdout] 1194 | atomic_cxchg!(atomic_cxchg, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1195:9 [INFO] [stdout] | [INFO] [stdout] 1195 | atomic_cxchg!(atomic_cxchg__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1196:9 [INFO] [stdout] | [INFO] [stdout] 1196 | atomic_cxchg!(atomic_cxchg__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1206:9 [INFO] [stdout] | [INFO] [stdout] 1206 | atomic_cxchg!(atomic_cxchg_acq__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1207:9 [INFO] [stdout] | [INFO] [stdout] 1207 | atomic_cxchg!(atomic_cxchg_acq__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1208:9 [INFO] [stdout] | [INFO] [stdout] 1208 | atomic_cxchg!(atomic_cxchg_acq__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1209:9 [INFO] [stdout] | [INFO] [stdout] 1209 | atomic_cxchg!(atomic_cxchg_acq__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1210:9 [INFO] [stdout] | [INFO] [stdout] 1210 | atomic_cxchg!(atomic_cxchg_acq__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1211:9 [INFO] [stdout] | [INFO] [stdout] 1211 | atomic_cxchg!(atomic_cxchg_acq__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1212:9 [INFO] [stdout] | [INFO] [stdout] 1212 | atomic_cxchg!(atomic_cxchg_acq__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1213:9 [INFO] [stdout] | [INFO] [stdout] 1213 | atomic_cxchg!(atomic_cxchg_acq__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1214:9 [INFO] [stdout] | [INFO] [stdout] 1214 | atomic_cxchg!(atomic_cxchg_acq__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1215:9 [INFO] [stdout] | [INFO] [stdout] 1215 | atomic_cxchg!(atomic_cxchg_acq, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1216:9 [INFO] [stdout] | [INFO] [stdout] 1216 | atomic_cxchg!(atomic_cxchg_acq__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1217:9 [INFO] [stdout] | [INFO] [stdout] 1217 | atomic_cxchg!(atomic_cxchg_acq__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1227:9 [INFO] [stdout] | [INFO] [stdout] 1227 | atomic_cxchg!(atomic_cxchg_rel__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1228:9 [INFO] [stdout] | [INFO] [stdout] 1228 | atomic_cxchg!(atomic_cxchg_rel__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1229:9 [INFO] [stdout] | [INFO] [stdout] 1229 | atomic_cxchg!(atomic_cxchg_rel__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1230:9 [INFO] [stdout] | [INFO] [stdout] 1230 | atomic_cxchg!(atomic_cxchg_rel__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1231:9 [INFO] [stdout] | [INFO] [stdout] 1231 | atomic_cxchg!(atomic_cxchg_rel__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1232:9 [INFO] [stdout] | [INFO] [stdout] 1232 | atomic_cxchg!(atomic_cxchg_rel__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1233:9 [INFO] [stdout] | [INFO] [stdout] 1233 | atomic_cxchg!(atomic_cxchg_rel__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1234:9 [INFO] [stdout] | [INFO] [stdout] 1234 | atomic_cxchg!(atomic_cxchg_rel__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1235:9 [INFO] [stdout] | [INFO] [stdout] 1235 | atomic_cxchg!(atomic_cxchg_rel__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1236:9 [INFO] [stdout] | [INFO] [stdout] 1236 | atomic_cxchg!(atomic_cxchg_rel, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1237:9 [INFO] [stdout] | [INFO] [stdout] 1237 | atomic_cxchg!(atomic_cxchg_rel__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1238:9 [INFO] [stdout] | [INFO] [stdout] 1238 | atomic_cxchg!(atomic_cxchg_rel__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1248:9 [INFO] [stdout] | [INFO] [stdout] 1248 | atomic_cxchg!(atomic_cxchg_acqrel__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1249:9 [INFO] [stdout] | [INFO] [stdout] 1249 | atomic_cxchg!(atomic_cxchg_acqrel__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1250:9 [INFO] [stdout] | [INFO] [stdout] 1250 | atomic_cxchg!(atomic_cxchg_acqrel__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1251:9 [INFO] [stdout] | [INFO] [stdout] 1251 | atomic_cxchg!(atomic_cxchg_acqrel__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1252:9 [INFO] [stdout] | [INFO] [stdout] 1252 | atomic_cxchg!(atomic_cxchg_acqrel__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1253:9 [INFO] [stdout] | [INFO] [stdout] 1253 | atomic_cxchg!(atomic_cxchg_acqrel__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1254:9 [INFO] [stdout] | [INFO] [stdout] 1254 | atomic_cxchg!(atomic_cxchg_acqrel__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1255:9 [INFO] [stdout] | [INFO] [stdout] 1255 | atomic_cxchg!(atomic_cxchg_acqrel__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1256:9 [INFO] [stdout] | [INFO] [stdout] 1256 | atomic_cxchg!(atomic_cxchg_acqrel__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1257:9 [INFO] [stdout] | [INFO] [stdout] 1257 | atomic_cxchg!(atomic_cxchg_acqrel, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1258:9 [INFO] [stdout] | [INFO] [stdout] 1258 | atomic_cxchg!(atomic_cxchg_acqrel__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1259:9 [INFO] [stdout] | [INFO] [stdout] 1259 | atomic_cxchg!(atomic_cxchg_acqrel__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1269:9 [INFO] [stdout] | [INFO] [stdout] 1269 | atomic_cxchg!(atomic_cxchg_relaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1270:9 [INFO] [stdout] | [INFO] [stdout] 1270 | atomic_cxchg!(atomic_cxchg_relaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1271:9 [INFO] [stdout] | [INFO] [stdout] 1271 | atomic_cxchg!(atomic_cxchg_relaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1272:9 [INFO] [stdout] | [INFO] [stdout] 1272 | atomic_cxchg!(atomic_cxchg_relaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1273:9 [INFO] [stdout] | [INFO] [stdout] 1273 | atomic_cxchg!(atomic_cxchg_relaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1274:9 [INFO] [stdout] | [INFO] [stdout] 1274 | atomic_cxchg!(atomic_cxchg_relaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1275:9 [INFO] [stdout] | [INFO] [stdout] 1275 | atomic_cxchg!(atomic_cxchg_relaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1276:9 [INFO] [stdout] | [INFO] [stdout] 1276 | atomic_cxchg!(atomic_cxchg_relaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1277:9 [INFO] [stdout] | [INFO] [stdout] 1277 | atomic_cxchg!(atomic_cxchg_relaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1278:9 [INFO] [stdout] | [INFO] [stdout] 1278 | atomic_cxchg!(atomic_cxchg_relaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1279:9 [INFO] [stdout] | [INFO] [stdout] 1279 | atomic_cxchg!(atomic_cxchg_relaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1280:9 [INFO] [stdout] | [INFO] [stdout] 1280 | atomic_cxchg!(atomic_cxchg_relaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1290:9 [INFO] [stdout] | [INFO] [stdout] 1290 | atomic_cxchg!(atomic_cxchg_failrelaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1291:9 [INFO] [stdout] | [INFO] [stdout] 1291 | atomic_cxchg!(atomic_cxchg_failrelaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1292:9 [INFO] [stdout] | [INFO] [stdout] 1292 | atomic_cxchg!(atomic_cxchg_failrelaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1293:9 [INFO] [stdout] | [INFO] [stdout] 1293 | atomic_cxchg!(atomic_cxchg_failrelaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1294:9 [INFO] [stdout] | [INFO] [stdout] 1294 | atomic_cxchg!(atomic_cxchg_failrelaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1295:9 [INFO] [stdout] | [INFO] [stdout] 1295 | atomic_cxchg!(atomic_cxchg_failrelaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1296:9 [INFO] [stdout] | [INFO] [stdout] 1296 | atomic_cxchg!(atomic_cxchg_failrelaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1297:9 [INFO] [stdout] | [INFO] [stdout] 1297 | atomic_cxchg!(atomic_cxchg_failrelaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1298:9 [INFO] [stdout] | [INFO] [stdout] 1298 | atomic_cxchg!(atomic_cxchg_failrelaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1299:9 [INFO] [stdout] | [INFO] [stdout] 1299 | atomic_cxchg!(atomic_cxchg_failrelaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1300:9 [INFO] [stdout] | [INFO] [stdout] 1300 | atomic_cxchg!(atomic_cxchg_failrelaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1301:9 [INFO] [stdout] | [INFO] [stdout] 1301 | atomic_cxchg!(atomic_cxchg_failrelaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1311:9 [INFO] [stdout] | [INFO] [stdout] 1311 | atomic_cxchg!(atomic_cxchg_failacq__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1312:9 [INFO] [stdout] | [INFO] [stdout] 1312 | atomic_cxchg!(atomic_cxchg_failacq__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1313:9 [INFO] [stdout] | [INFO] [stdout] 1313 | atomic_cxchg!(atomic_cxchg_failacq__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1314:9 [INFO] [stdout] | [INFO] [stdout] 1314 | atomic_cxchg!(atomic_cxchg_failacq__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1315:9 [INFO] [stdout] | [INFO] [stdout] 1315 | atomic_cxchg!(atomic_cxchg_failacq__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1316:9 [INFO] [stdout] | [INFO] [stdout] 1316 | atomic_cxchg!(atomic_cxchg_failacq__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1317:9 [INFO] [stdout] | [INFO] [stdout] 1317 | atomic_cxchg!(atomic_cxchg_failacq__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1318:9 [INFO] [stdout] | [INFO] [stdout] 1318 | atomic_cxchg!(atomic_cxchg_failacq__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1319:9 [INFO] [stdout] | [INFO] [stdout] 1319 | atomic_cxchg!(atomic_cxchg_failacq__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1320:9 [INFO] [stdout] | [INFO] [stdout] 1320 | atomic_cxchg!(atomic_cxchg_failacq, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1321:9 [INFO] [stdout] | [INFO] [stdout] 1321 | atomic_cxchg!(atomic_cxchg_failacq__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1322:9 [INFO] [stdout] | [INFO] [stdout] 1322 | atomic_cxchg!(atomic_cxchg_failacq__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1332:9 [INFO] [stdout] | [INFO] [stdout] 1332 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1333:9 [INFO] [stdout] | [INFO] [stdout] 1333 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1334:9 [INFO] [stdout] | [INFO] [stdout] 1334 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1335:9 [INFO] [stdout] | [INFO] [stdout] 1335 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1336:9 [INFO] [stdout] | [INFO] [stdout] 1336 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1337:9 [INFO] [stdout] | [INFO] [stdout] 1337 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1338:9 [INFO] [stdout] | [INFO] [stdout] 1338 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1339:9 [INFO] [stdout] | [INFO] [stdout] 1339 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1340:9 [INFO] [stdout] | [INFO] [stdout] 1340 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1341:9 [INFO] [stdout] | [INFO] [stdout] 1341 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1342:9 [INFO] [stdout] | [INFO] [stdout] 1342 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1343:9 [INFO] [stdout] | [INFO] [stdout] 1343 | atomic_cxchg!(atomic_cxchg_acq_failrelaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1353:9 [INFO] [stdout] | [INFO] [stdout] 1353 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1354:9 [INFO] [stdout] | [INFO] [stdout] 1354 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1355:9 [INFO] [stdout] | [INFO] [stdout] 1355 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1356:9 [INFO] [stdout] | [INFO] [stdout] 1356 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1357:9 [INFO] [stdout] | [INFO] [stdout] 1357 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1358:9 [INFO] [stdout] | [INFO] [stdout] 1358 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1359:9 [INFO] [stdout] | [INFO] [stdout] 1359 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1360:9 [INFO] [stdout] | [INFO] [stdout] 1360 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1361:9 [INFO] [stdout] | [INFO] [stdout] 1361 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1362:9 [INFO] [stdout] | [INFO] [stdout] 1362 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1363:9 [INFO] [stdout] | [INFO] [stdout] 1363 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1364:9 [INFO] [stdout] | [INFO] [stdout] 1364 | atomic_cxchg!(atomic_cxchg_acqrel_failrelaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1374:9 [INFO] [stdout] | [INFO] [stdout] 1374 | atomic_cxchg!(atomic_cxchgweak__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1375:9 [INFO] [stdout] | [INFO] [stdout] 1375 | atomic_cxchg!(atomic_cxchgweak__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1376:9 [INFO] [stdout] | [INFO] [stdout] 1376 | atomic_cxchg!(atomic_cxchgweak__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1377:9 [INFO] [stdout] | [INFO] [stdout] 1377 | atomic_cxchg!(atomic_cxchgweak__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1378:9 [INFO] [stdout] | [INFO] [stdout] 1378 | atomic_cxchg!(atomic_cxchgweak__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1379:9 [INFO] [stdout] | [INFO] [stdout] 1379 | atomic_cxchg!(atomic_cxchgweak__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1380:9 [INFO] [stdout] | [INFO] [stdout] 1380 | atomic_cxchg!(atomic_cxchgweak__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1381:9 [INFO] [stdout] | [INFO] [stdout] 1381 | atomic_cxchg!(atomic_cxchgweak__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1382:9 [INFO] [stdout] | [INFO] [stdout] 1382 | atomic_cxchg!(atomic_cxchgweak__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1383:9 [INFO] [stdout] | [INFO] [stdout] 1383 | atomic_cxchg!(atomic_cxchgweak, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1384:9 [INFO] [stdout] | [INFO] [stdout] 1384 | atomic_cxchg!(atomic_cxchgweak__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1385:9 [INFO] [stdout] | [INFO] [stdout] 1385 | atomic_cxchg!(atomic_cxchgweak__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1395:9 [INFO] [stdout] | [INFO] [stdout] 1395 | atomic_cxchg!(atomic_cxchgweak_acq__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1396:9 [INFO] [stdout] | [INFO] [stdout] 1396 | atomic_cxchg!(atomic_cxchgweak_acq__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1397:9 [INFO] [stdout] | [INFO] [stdout] 1397 | atomic_cxchg!(atomic_cxchgweak_acq__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1398:9 [INFO] [stdout] | [INFO] [stdout] 1398 | atomic_cxchg!(atomic_cxchgweak_acq__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1399:9 [INFO] [stdout] | [INFO] [stdout] 1399 | atomic_cxchg!(atomic_cxchgweak_acq__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1400:9 [INFO] [stdout] | [INFO] [stdout] 1400 | atomic_cxchg!(atomic_cxchgweak_acq__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1401:9 [INFO] [stdout] | [INFO] [stdout] 1401 | atomic_cxchg!(atomic_cxchgweak_acq__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1402:9 [INFO] [stdout] | [INFO] [stdout] 1402 | atomic_cxchg!(atomic_cxchgweak_acq__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1403:9 [INFO] [stdout] | [INFO] [stdout] 1403 | atomic_cxchg!(atomic_cxchgweak_acq__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1404:9 [INFO] [stdout] | [INFO] [stdout] 1404 | atomic_cxchg!(atomic_cxchgweak_acq, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1405:9 [INFO] [stdout] | [INFO] [stdout] 1405 | atomic_cxchg!(atomic_cxchgweak_acq__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1406:9 [INFO] [stdout] | [INFO] [stdout] 1406 | atomic_cxchg!(atomic_cxchgweak_acq__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1416:9 [INFO] [stdout] | [INFO] [stdout] 1416 | atomic_cxchg!(atomic_cxchgweak_rel__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1417:9 [INFO] [stdout] | [INFO] [stdout] 1417 | atomic_cxchg!(atomic_cxchgweak_rel__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1418:9 [INFO] [stdout] | [INFO] [stdout] 1418 | atomic_cxchg!(atomic_cxchgweak_rel__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1419:9 [INFO] [stdout] | [INFO] [stdout] 1419 | atomic_cxchg!(atomic_cxchgweak_rel__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1420:9 [INFO] [stdout] | [INFO] [stdout] 1420 | atomic_cxchg!(atomic_cxchgweak_rel__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1421:9 [INFO] [stdout] | [INFO] [stdout] 1421 | atomic_cxchg!(atomic_cxchgweak_rel__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1422:9 [INFO] [stdout] | [INFO] [stdout] 1422 | atomic_cxchg!(atomic_cxchgweak_rel__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1423:9 [INFO] [stdout] | [INFO] [stdout] 1423 | atomic_cxchg!(atomic_cxchgweak_rel__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1424:9 [INFO] [stdout] | [INFO] [stdout] 1424 | atomic_cxchg!(atomic_cxchgweak_rel__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1425:9 [INFO] [stdout] | [INFO] [stdout] 1425 | atomic_cxchg!(atomic_cxchgweak_rel, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1426:9 [INFO] [stdout] | [INFO] [stdout] 1426 | atomic_cxchg!(atomic_cxchgweak_rel__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1427:9 [INFO] [stdout] | [INFO] [stdout] 1427 | atomic_cxchg!(atomic_cxchgweak_rel__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1437:9 [INFO] [stdout] | [INFO] [stdout] 1437 | atomic_cxchg!(atomic_cxchgweak_acqrel__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1438:9 [INFO] [stdout] | [INFO] [stdout] 1438 | atomic_cxchg!(atomic_cxchgweak_acqrel__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1439:9 [INFO] [stdout] | [INFO] [stdout] 1439 | atomic_cxchg!(atomic_cxchgweak_acqrel__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1440:9 [INFO] [stdout] | [INFO] [stdout] 1440 | atomic_cxchg!(atomic_cxchgweak_acqrel__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1441:9 [INFO] [stdout] | [INFO] [stdout] 1441 | atomic_cxchg!(atomic_cxchgweak_acqrel__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1442:9 [INFO] [stdout] | [INFO] [stdout] 1442 | atomic_cxchg!(atomic_cxchgweak_acqrel__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1443:9 [INFO] [stdout] | [INFO] [stdout] 1443 | atomic_cxchg!(atomic_cxchgweak_acqrel__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1444:9 [INFO] [stdout] | [INFO] [stdout] 1444 | atomic_cxchg!(atomic_cxchgweak_acqrel__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1445:9 [INFO] [stdout] | [INFO] [stdout] 1445 | atomic_cxchg!(atomic_cxchgweak_acqrel__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1446:9 [INFO] [stdout] | [INFO] [stdout] 1446 | atomic_cxchg!(atomic_cxchgweak_acqrel, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1447:9 [INFO] [stdout] | [INFO] [stdout] 1447 | atomic_cxchg!(atomic_cxchgweak_acqrel__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1448:9 [INFO] [stdout] | [INFO] [stdout] 1448 | atomic_cxchg!(atomic_cxchgweak_acqrel__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1458:9 [INFO] [stdout] | [INFO] [stdout] 1458 | atomic_cxchg!(atomic_cxchgweak_relaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1459:9 [INFO] [stdout] | [INFO] [stdout] 1459 | atomic_cxchg!(atomic_cxchgweak_relaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1460:9 [INFO] [stdout] | [INFO] [stdout] 1460 | atomic_cxchg!(atomic_cxchgweak_relaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1461:9 [INFO] [stdout] | [INFO] [stdout] 1461 | atomic_cxchg!(atomic_cxchgweak_relaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1462:9 [INFO] [stdout] | [INFO] [stdout] 1462 | atomic_cxchg!(atomic_cxchgweak_relaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1463:9 [INFO] [stdout] | [INFO] [stdout] 1463 | atomic_cxchg!(atomic_cxchgweak_relaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1464:9 [INFO] [stdout] | [INFO] [stdout] 1464 | atomic_cxchg!(atomic_cxchgweak_relaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1465:9 [INFO] [stdout] | [INFO] [stdout] 1465 | atomic_cxchg!(atomic_cxchgweak_relaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1466:9 [INFO] [stdout] | [INFO] [stdout] 1466 | atomic_cxchg!(atomic_cxchgweak_relaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1467:9 [INFO] [stdout] | [INFO] [stdout] 1467 | atomic_cxchg!(atomic_cxchgweak_relaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1468:9 [INFO] [stdout] | [INFO] [stdout] 1468 | atomic_cxchg!(atomic_cxchgweak_relaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1469:9 [INFO] [stdout] | [INFO] [stdout] 1469 | atomic_cxchg!(atomic_cxchgweak_relaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1479:9 [INFO] [stdout] | [INFO] [stdout] 1479 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1480:9 [INFO] [stdout] | [INFO] [stdout] 1480 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1481:9 [INFO] [stdout] | [INFO] [stdout] 1481 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1482:9 [INFO] [stdout] | [INFO] [stdout] 1482 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1483:9 [INFO] [stdout] | [INFO] [stdout] 1483 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1484:9 [INFO] [stdout] | [INFO] [stdout] 1484 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1485:9 [INFO] [stdout] | [INFO] [stdout] 1485 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1486:9 [INFO] [stdout] | [INFO] [stdout] 1486 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1487:9 [INFO] [stdout] | [INFO] [stdout] 1487 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1488:9 [INFO] [stdout] | [INFO] [stdout] 1488 | atomic_cxchg!(atomic_cxchgweak_failrelaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1489:9 [INFO] [stdout] | [INFO] [stdout] 1489 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1490:9 [INFO] [stdout] | [INFO] [stdout] 1490 | atomic_cxchg!(atomic_cxchgweak_failrelaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1500:9 [INFO] [stdout] | [INFO] [stdout] 1500 | atomic_cxchg!(atomic_cxchgweak_failacq__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1501:9 [INFO] [stdout] | [INFO] [stdout] 1501 | atomic_cxchg!(atomic_cxchgweak_failacq__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1502:9 [INFO] [stdout] | [INFO] [stdout] 1502 | atomic_cxchg!(atomic_cxchgweak_failacq__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1503:9 [INFO] [stdout] | [INFO] [stdout] 1503 | atomic_cxchg!(atomic_cxchgweak_failacq__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1504:9 [INFO] [stdout] | [INFO] [stdout] 1504 | atomic_cxchg!(atomic_cxchgweak_failacq__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1505:9 [INFO] [stdout] | [INFO] [stdout] 1505 | atomic_cxchg!(atomic_cxchgweak_failacq__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1506:9 [INFO] [stdout] | [INFO] [stdout] 1506 | atomic_cxchg!(atomic_cxchgweak_failacq__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1507:9 [INFO] [stdout] | [INFO] [stdout] 1507 | atomic_cxchg!(atomic_cxchgweak_failacq__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1508:9 [INFO] [stdout] | [INFO] [stdout] 1508 | atomic_cxchg!(atomic_cxchgweak_failacq__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1509:9 [INFO] [stdout] | [INFO] [stdout] 1509 | atomic_cxchg!(atomic_cxchgweak_failacq, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1510:9 [INFO] [stdout] | [INFO] [stdout] 1510 | atomic_cxchg!(atomic_cxchgweak_failacq__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1511:9 [INFO] [stdout] | [INFO] [stdout] 1511 | atomic_cxchg!(atomic_cxchgweak_failacq__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1525:9 [INFO] [stdout] | [INFO] [stdout] 1525 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1526:9 [INFO] [stdout] | [INFO] [stdout] 1526 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1527:9 [INFO] [stdout] | [INFO] [stdout] 1527 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1528:9 [INFO] [stdout] | [INFO] [stdout] 1528 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1529:9 [INFO] [stdout] | [INFO] [stdout] 1529 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1530:9 [INFO] [stdout] | [INFO] [stdout] 1530 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1531:9 [INFO] [stdout] | [INFO] [stdout] 1531 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1532:9 [INFO] [stdout] | [INFO] [stdout] 1532 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1533:9 [INFO] [stdout] | [INFO] [stdout] 1533 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1534:9 [INFO] [stdout] | [INFO] [stdout] 1534 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1535:9 [INFO] [stdout] | [INFO] [stdout] 1535 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1536:9 [INFO] [stdout] | [INFO] [stdout] 1536 | atomic_cxchg!(atomic_cxchgweak_acq_failrelaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1550:9 [INFO] [stdout] | [INFO] [stdout] 1550 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__i8, i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1551:9 [INFO] [stdout] | [INFO] [stdout] 1551 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__i16, i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1552:9 [INFO] [stdout] | [INFO] [stdout] 1552 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__i32, i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1553:9 [INFO] [stdout] | [INFO] [stdout] 1553 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__i64, i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1554:9 [INFO] [stdout] | [INFO] [stdout] 1554 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__isize, isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1555:9 [INFO] [stdout] | [INFO] [stdout] 1555 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__u8, u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1556:9 [INFO] [stdout] | [INFO] [stdout] 1556 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__u16, u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1557:9 [INFO] [stdout] | [INFO] [stdout] 1557 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__u32, u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1558:9 [INFO] [stdout] | [INFO] [stdout] 1558 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__u64, u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1559:9 [INFO] [stdout] | [INFO] [stdout] 1559 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed, usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1560:9 [INFO] [stdout] | [INFO] [stdout] 1560 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__i128, i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:1561:9 [INFO] [stdout] | [INFO] [stdout] 1561 | atomic_cxchg!(atomic_cxchgweak_acqrel_failrelaxed__u128, u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `abstract_value` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `abstract_value` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `abstract_value` which comes from the expansion of the macro `atomic_cxchg` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2546:9 [INFO] [stdout] | [INFO] [stdout] 2546 | default_contract!(prefetch_read_data); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2547:9 [INFO] [stdout] | [INFO] [stdout] 2547 | default_contract!(prefetch_write_data); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2548:9 [INFO] [stdout] | [INFO] [stdout] 2548 | default_contract!(prefetch_read_instruction); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2549:9 [INFO] [stdout] | [INFO] [stdout] 2549 | default_contract!(prefetch_write_instruction); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2552:13 [INFO] [stdout] | [INFO] [stdout] 2552 | default_contract!(assert_inhabited); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2553:13 [INFO] [stdout] | [INFO] [stdout] 2553 | default_contract!(assert_zero_valid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2554:13 [INFO] [stdout] | [INFO] [stdout] 2554 | default_contract!(assert_uninit_valid); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2555:13 [INFO] [stdout] | [INFO] [stdout] 2555 | default_contract!(atomic_fence); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2556:13 [INFO] [stdout] | [INFO] [stdout] 2556 | default_contract!(atomic_fence_acq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2557:13 [INFO] [stdout] | [INFO] [stdout] 2557 | default_contract!(atomic_fence_rel); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2558:13 [INFO] [stdout] | [INFO] [stdout] 2558 | default_contract!(atomic_fence_acqrel); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2559:13 [INFO] [stdout] | [INFO] [stdout] 2559 | default_contract!(atomic_singlethreadfence); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2560:13 [INFO] [stdout] | [INFO] [stdout] 2560 | default_contract!(atomic_singlethreadfence_acq); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2561:13 [INFO] [stdout] | [INFO] [stdout] 2561 | default_contract!(atomic_singlethreadfence_rel); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2562:13 [INFO] [stdout] | [INFO] [stdout] 2562 | default_contract!(atomic_singlethreadfence_acqrel); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2563:13 [INFO] [stdout] | [INFO] [stdout] 2563 | default_contract!(rustc_peek); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2565:17 [INFO] [stdout] | [INFO] [stdout] 2565 | assume_unreachable!(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume_unreachable` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume_unreachable` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume_unreachable` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2568:17 [INFO] [stdout] | [INFO] [stdout] 2568 | assume_unreachable!(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume_unreachable` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume_unreachable` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume_unreachable` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2571:17 [INFO] [stdout] | [INFO] [stdout] 2571 | assumed_postcondition!(b); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assumed_postcondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assumed_postcondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assumed_postcondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2571:17 [INFO] [stdout] | [INFO] [stdout] 2571 | assumed_postcondition!(b); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assumed_postcondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assumed_postcondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assumed_postcondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2579:13 [INFO] [stdout] | [INFO] [stdout] 2579 | default_contract!(breakpoint); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2594:17 [INFO] [stdout] | [INFO] [stdout] 2594 | result!() [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2597:17 [INFO] [stdout] | [INFO] [stdout] 2597 | result!() [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2602:13 [INFO] [stdout] | [INFO] [stdout] 2602 | default_contract!(caller_location); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2603:13 [INFO] [stdout] | [INFO] [stdout] 2603 | default_contract!(init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2604:13 [INFO] [stdout] | [INFO] [stdout] 2604 | default_contract!(uninit); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2630:13 [INFO] [stdout] | [INFO] [stdout] 2630 | default_contract!(float_to_int_unchecked); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2648:13 [INFO] [stdout] | [INFO] [stdout] 2648 | default_contract!(add_with_overflow__i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2649:13 [INFO] [stdout] | [INFO] [stdout] 2649 | default_contract!(add_with_overflow__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2661:13 [INFO] [stdout] | [INFO] [stdout] 2661 | default_contract!(sub_with_overflow__i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2662:13 [INFO] [stdout] | [INFO] [stdout] 2662 | default_contract!(sub_with_overflow__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2666:13 [INFO] [stdout] | [INFO] [stdout] 2666 | exact_signed_div!(i8, exact_div__i8, i8::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2666:13 [INFO] [stdout] | [INFO] [stdout] 2666 | exact_signed_div!(i8, exact_div__i8, i8::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2666:13 [INFO] [stdout] | [INFO] [stdout] 2666 | exact_signed_div!(i8, exact_div__i8, i8::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2667:13 [INFO] [stdout] | [INFO] [stdout] 2667 | exact_signed_div!(i16, exact_div__i16, i16::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2667:13 [INFO] [stdout] | [INFO] [stdout] 2667 | exact_signed_div!(i16, exact_div__i16, i16::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2667:13 [INFO] [stdout] | [INFO] [stdout] 2667 | exact_signed_div!(i16, exact_div__i16, i16::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2668:13 [INFO] [stdout] | [INFO] [stdout] 2668 | exact_signed_div!(i32, exact_div__i32, i32::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2668:13 [INFO] [stdout] | [INFO] [stdout] 2668 | exact_signed_div!(i32, exact_div__i32, i32::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2668:13 [INFO] [stdout] | [INFO] [stdout] 2668 | exact_signed_div!(i32, exact_div__i32, i32::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2669:13 [INFO] [stdout] | [INFO] [stdout] 2669 | exact_signed_div!(i64, exact_div__i64, i64::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2669:13 [INFO] [stdout] | [INFO] [stdout] 2669 | exact_signed_div!(i64, exact_div__i64, i64::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2669:13 [INFO] [stdout] | [INFO] [stdout] 2669 | exact_signed_div!(i64, exact_div__i64, i64::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2670:13 [INFO] [stdout] | [INFO] [stdout] 2670 | exact_signed_div!(i128, exact_div__i128, i128::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2670:13 [INFO] [stdout] | [INFO] [stdout] 2670 | exact_signed_div!(i128, exact_div__i128, i128::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2670:13 [INFO] [stdout] | [INFO] [stdout] 2670 | exact_signed_div!(i128, exact_div__i128, i128::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2671:13 [INFO] [stdout] | [INFO] [stdout] 2671 | exact_signed_div!(isize, exact_div__isize, isize::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2671:13 [INFO] [stdout] | [INFO] [stdout] 2671 | exact_signed_div!(isize, exact_div__isize, isize::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2671:13 [INFO] [stdout] | [INFO] [stdout] 2671 | exact_signed_div!(isize, exact_div__isize, isize::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2672:13 [INFO] [stdout] | [INFO] [stdout] 2672 | exact_div!(u8, exact_div__u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2672:13 [INFO] [stdout] | [INFO] [stdout] 2672 | exact_div!(u8, exact_div__u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2673:13 [INFO] [stdout] | [INFO] [stdout] 2673 | exact_div!(u16, exact_div__u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2673:13 [INFO] [stdout] | [INFO] [stdout] 2673 | exact_div!(u16, exact_div__u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2674:13 [INFO] [stdout] | [INFO] [stdout] 2674 | exact_div!(u32, exact_div__u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2674:13 [INFO] [stdout] | [INFO] [stdout] 2674 | exact_div!(u32, exact_div__u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2675:13 [INFO] [stdout] | [INFO] [stdout] 2675 | exact_div!(u64, exact_div__u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2675:13 [INFO] [stdout] | [INFO] [stdout] 2675 | exact_div!(u64, exact_div__u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2676:13 [INFO] [stdout] | [INFO] [stdout] 2676 | exact_div!(u128, exact_div__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2676:13 [INFO] [stdout] | [INFO] [stdout] 2676 | exact_div!(u128, exact_div__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2677:13 [INFO] [stdout] | [INFO] [stdout] 2677 | exact_div!(usize, exact_div__usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2677:13 [INFO] [stdout] | [INFO] [stdout] 2677 | exact_div!(usize, exact_div__usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `exact_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2679:13 [INFO] [stdout] | [INFO] [stdout] 2679 | unchecked_signed_div!(i8, unchecked_div__i8, i8::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2679:13 [INFO] [stdout] | [INFO] [stdout] 2679 | unchecked_signed_div!(i8, unchecked_div__i8, i8::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2680:13 [INFO] [stdout] | [INFO] [stdout] 2680 | unchecked_signed_div!(i16, unchecked_div__i16, i16::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2680:13 [INFO] [stdout] | [INFO] [stdout] 2680 | unchecked_signed_div!(i16, unchecked_div__i16, i16::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2681:13 [INFO] [stdout] | [INFO] [stdout] 2681 | unchecked_signed_div!(i32, unchecked_div__i32, i32::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2681:13 [INFO] [stdout] | [INFO] [stdout] 2681 | unchecked_signed_div!(i32, unchecked_div__i32, i32::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2682:13 [INFO] [stdout] | [INFO] [stdout] 2682 | unchecked_signed_div!(i64, unchecked_div__i64, i64::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2682:13 [INFO] [stdout] | [INFO] [stdout] 2682 | unchecked_signed_div!(i64, unchecked_div__i64, i64::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2683:13 [INFO] [stdout] | [INFO] [stdout] 2683 | unchecked_signed_div!(i128, unchecked_div__i128, i128::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2683:13 [INFO] [stdout] | [INFO] [stdout] 2683 | unchecked_signed_div!(i128, unchecked_div__i128, i128::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2684:13 [INFO] [stdout] | [INFO] [stdout] 2684 | unchecked_signed_div!(isize, unchecked_div__isize, isize::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2684:13 [INFO] [stdout] | [INFO] [stdout] 2684 | unchecked_signed_div!(isize, unchecked_div__isize, isize::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2685:13 [INFO] [stdout] | [INFO] [stdout] 2685 | unchecked_div!(u8, unchecked_div__u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2686:13 [INFO] [stdout] | [INFO] [stdout] 2686 | unchecked_div!(u16, unchecked_div__u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2687:13 [INFO] [stdout] | [INFO] [stdout] 2687 | unchecked_div!(u32, unchecked_div__u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2688:13 [INFO] [stdout] | [INFO] [stdout] 2688 | unchecked_div!(u64, unchecked_div__u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2689:13 [INFO] [stdout] | [INFO] [stdout] 2689 | unchecked_div!(u128, unchecked_div__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2690:13 [INFO] [stdout] | [INFO] [stdout] 2690 | unchecked_div!(usize, unchecked_div__usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_div` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2692:13 [INFO] [stdout] | [INFO] [stdout] 2692 | unchecked_signed_rem!(i8, unchecked_rem__i8, i8::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2692:13 [INFO] [stdout] | [INFO] [stdout] 2692 | unchecked_signed_rem!(i8, unchecked_rem__i8, i8::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2693:13 [INFO] [stdout] | [INFO] [stdout] 2693 | unchecked_signed_rem!(i16, unchecked_rem__i16, i16::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2693:13 [INFO] [stdout] | [INFO] [stdout] 2693 | unchecked_signed_rem!(i16, unchecked_rem__i16, i16::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2694:13 [INFO] [stdout] | [INFO] [stdout] 2694 | unchecked_signed_rem!(i32, unchecked_rem__i32, i32::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2694:13 [INFO] [stdout] | [INFO] [stdout] 2694 | unchecked_signed_rem!(i32, unchecked_rem__i32, i32::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2695:13 [INFO] [stdout] | [INFO] [stdout] 2695 | unchecked_signed_rem!(i64, unchecked_rem__i64, i64::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2695:13 [INFO] [stdout] | [INFO] [stdout] 2695 | unchecked_signed_rem!(i64, unchecked_rem__i64, i64::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2696:13 [INFO] [stdout] | [INFO] [stdout] 2696 | unchecked_signed_rem!(i128, unchecked_rem__i128, i128::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2696:13 [INFO] [stdout] | [INFO] [stdout] 2696 | unchecked_signed_rem!(i128, unchecked_rem__i128, i128::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2697:13 [INFO] [stdout] | [INFO] [stdout] 2697 | unchecked_signed_rem!(isize, unchecked_rem__isize, isize::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2697:13 [INFO] [stdout] | [INFO] [stdout] 2697 | unchecked_signed_rem!(isize, unchecked_rem__isize, isize::MIN); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_signed_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2698:13 [INFO] [stdout] | [INFO] [stdout] 2698 | unchecked_rem!(u8, unchecked_rem__u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2699:13 [INFO] [stdout] | [INFO] [stdout] 2699 | unchecked_rem!(u16, unchecked_rem__u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2700:13 [INFO] [stdout] | [INFO] [stdout] 2700 | unchecked_rem!(u32, unchecked_rem__u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2701:13 [INFO] [stdout] | [INFO] [stdout] 2701 | unchecked_rem!(u64, unchecked_rem__u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2702:13 [INFO] [stdout] | [INFO] [stdout] 2702 | unchecked_rem!(u128, unchecked_rem__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2703:13 [INFO] [stdout] | [INFO] [stdout] 2703 | unchecked_rem!(usize, unchecked_rem__usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_rem` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2705:13 [INFO] [stdout] | [INFO] [stdout] 2705 | unchecked_shl!(i8, unchecked_shl__i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2706:13 [INFO] [stdout] | [INFO] [stdout] 2706 | unchecked_shl!(i16, unchecked_shl__i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2707:13 [INFO] [stdout] | [INFO] [stdout] 2707 | unchecked_shl!(i32, unchecked_shl__i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2708:13 [INFO] [stdout] | [INFO] [stdout] 2708 | unchecked_shl!(i64, unchecked_shl__i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2709:13 [INFO] [stdout] | [INFO] [stdout] 2709 | unchecked_shl!(i128, unchecked_shl__i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2710:13 [INFO] [stdout] | [INFO] [stdout] 2710 | unchecked_shl!(isize, unchecked_shl__isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2711:13 [INFO] [stdout] | [INFO] [stdout] 2711 | unchecked_shl!(u8, unchecked_shl__u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2712:13 [INFO] [stdout] | [INFO] [stdout] 2712 | unchecked_shl!(u16, unchecked_shl__u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2713:13 [INFO] [stdout] | [INFO] [stdout] 2713 | unchecked_shl!(u32, unchecked_shl__u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2714:13 [INFO] [stdout] | [INFO] [stdout] 2714 | unchecked_shl!(u64, unchecked_shl__u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2715:13 [INFO] [stdout] | [INFO] [stdout] 2715 | unchecked_shl!(u128, unchecked_shl__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2716:13 [INFO] [stdout] | [INFO] [stdout] 2716 | unchecked_shl!(usize, unchecked_shl__usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2718:13 [INFO] [stdout] | [INFO] [stdout] 2718 | unchecked_shr!(i8, unchecked_shr__i8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2719:13 [INFO] [stdout] | [INFO] [stdout] 2719 | unchecked_shr!(i16, unchecked_shr__i16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2720:13 [INFO] [stdout] | [INFO] [stdout] 2720 | unchecked_shr!(i32, unchecked_shr__i32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2721:13 [INFO] [stdout] | [INFO] [stdout] 2721 | unchecked_shr!(i64, unchecked_shr__i64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2722:13 [INFO] [stdout] | [INFO] [stdout] 2722 | unchecked_shr!(i128, unchecked_shr__i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2723:13 [INFO] [stdout] | [INFO] [stdout] 2723 | unchecked_shr!(isize, unchecked_shr__isize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2724:13 [INFO] [stdout] | [INFO] [stdout] 2724 | unchecked_shr!(u8, unchecked_shr__u8); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2725:13 [INFO] [stdout] | [INFO] [stdout] 2725 | unchecked_shr!(u16, unchecked_shr__u16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2726:13 [INFO] [stdout] | [INFO] [stdout] 2726 | unchecked_shr!(u32, unchecked_shr__u32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2727:13 [INFO] [stdout] | [INFO] [stdout] 2727 | unchecked_shr!(u64, unchecked_shr__u64); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2728:13 [INFO] [stdout] | [INFO] [stdout] 2728 | unchecked_shr!(u128, unchecked_shr__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2729:13 [INFO] [stdout] | [INFO] [stdout] 2729 | unchecked_shr!(usize, unchecked_shr__usize); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_shr` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2731:13 [INFO] [stdout] | [INFO] [stdout] 2731 | unchecked_add!(i8, i128, unchecked_add__i8, i8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2732:13 [INFO] [stdout] | [INFO] [stdout] 2732 | unchecked_add!(i16, i128, unchecked_add__i16, i16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2733:13 [INFO] [stdout] | [INFO] [stdout] 2733 | unchecked_add!(i32, i128, unchecked_add__i32, i32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2734:13 [INFO] [stdout] | [INFO] [stdout] 2734 | unchecked_add!(i64, i128, unchecked_add__i64, i64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2735:13 [INFO] [stdout] | [INFO] [stdout] 2735 | unchecked_add!(i128, i128, unchecked_add__i128, i128::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2736:13 [INFO] [stdout] | [INFO] [stdout] 2736 | unchecked_add!(isize, i128, unchecked_add__isize, i128::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2737:13 [INFO] [stdout] | [INFO] [stdout] 2737 | unchecked_add!(u8, u128, unchecked_add__u8, u8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2738:13 [INFO] [stdout] | [INFO] [stdout] 2738 | unchecked_add!(u16, u128, unchecked_add__u16, u16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2739:13 [INFO] [stdout] | [INFO] [stdout] 2739 | unchecked_add!(u32, u128, unchecked_add__u32, u32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2740:13 [INFO] [stdout] | [INFO] [stdout] 2740 | unchecked_add!(u64, u128, unchecked_add__u64, u64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2741:13 [INFO] [stdout] | [INFO] [stdout] 2741 | unchecked_add!(u128, u128, unchecked_add__u128, u128::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2742:13 [INFO] [stdout] | [INFO] [stdout] 2742 | unchecked_add!(usize, u128, unchecked_add__usize, usize::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_add` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2744:13 [INFO] [stdout] | [INFO] [stdout] 2744 | unchecked_sub!(i8, unchecked_sub__i8, i8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2744:13 [INFO] [stdout] | [INFO] [stdout] 2744 | unchecked_sub!(i8, unchecked_sub__i8, i8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2745:13 [INFO] [stdout] | [INFO] [stdout] 2745 | unchecked_sub!(i16, unchecked_sub__i16, i16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2745:13 [INFO] [stdout] | [INFO] [stdout] 2745 | unchecked_sub!(i16, unchecked_sub__i16, i16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2746:13 [INFO] [stdout] | [INFO] [stdout] 2746 | unchecked_sub!(i32, unchecked_sub__i32, i32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2746:13 [INFO] [stdout] | [INFO] [stdout] 2746 | unchecked_sub!(i32, unchecked_sub__i32, i32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2747:13 [INFO] [stdout] | [INFO] [stdout] 2747 | unchecked_sub!(i64, unchecked_sub__i64, i64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2747:13 [INFO] [stdout] | [INFO] [stdout] 2747 | unchecked_sub!(i64, unchecked_sub__i64, i64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2748:13 [INFO] [stdout] | [INFO] [stdout] 2748 | unchecked_sub!(isize, unchecked_sub__isize, i128::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2748:13 [INFO] [stdout] | [INFO] [stdout] 2748 | unchecked_sub!(isize, unchecked_sub__isize, i128::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2749:13 [INFO] [stdout] | [INFO] [stdout] 2749 | unchecked_sub!(u8, unchecked_sub__u8, u8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2749:13 [INFO] [stdout] | [INFO] [stdout] 2749 | unchecked_sub!(u8, unchecked_sub__u8, u8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2750:13 [INFO] [stdout] | [INFO] [stdout] 2750 | unchecked_sub!(u16, unchecked_sub__u16, u16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2750:13 [INFO] [stdout] | [INFO] [stdout] 2750 | unchecked_sub!(u16, unchecked_sub__u16, u16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2751:13 [INFO] [stdout] | [INFO] [stdout] 2751 | unchecked_sub!(u32, unchecked_sub__u32, u32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2751:13 [INFO] [stdout] | [INFO] [stdout] 2751 | unchecked_sub!(u32, unchecked_sub__u32, u32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2752:13 [INFO] [stdout] | [INFO] [stdout] 2752 | unchecked_sub!(u64, unchecked_sub__u64, u64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2752:13 [INFO] [stdout] | [INFO] [stdout] 2752 | unchecked_sub!(u64, unchecked_sub__u64, u64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_sub` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2761:13 [INFO] [stdout] | [INFO] [stdout] 2761 | unchecked_mul!(i8, i128, unchecked_mul__i8, i8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2762:13 [INFO] [stdout] | [INFO] [stdout] 2762 | unchecked_mul!(i16, i128, unchecked_mul__i16, i16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2763:13 [INFO] [stdout] | [INFO] [stdout] 2763 | unchecked_mul!(i32, i128, unchecked_mul__i32, i32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2764:13 [INFO] [stdout] | [INFO] [stdout] 2764 | unchecked_mul!(i64, i128, unchecked_mul__i64, i64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2765:13 [INFO] [stdout] | [INFO] [stdout] 2765 | unchecked_mul!(i128, i128, unchecked_mul__i128, i128::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2766:13 [INFO] [stdout] | [INFO] [stdout] 2766 | unchecked_mul!(isize, i128, unchecked_mul__isize, isize::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2767:13 [INFO] [stdout] | [INFO] [stdout] 2767 | unchecked_mul!(u8, u128, unchecked_mul__u8, u8::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2768:13 [INFO] [stdout] | [INFO] [stdout] 2768 | unchecked_mul!(u16, u128, unchecked_mul__u16, u16::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2769:13 [INFO] [stdout] | [INFO] [stdout] 2769 | unchecked_mul!(u32, u128, unchecked_mul__u32, u32::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2770:13 [INFO] [stdout] | [INFO] [stdout] 2770 | unchecked_mul!(u64, u128, unchecked_mul__u64, u64::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2771:13 [INFO] [stdout] | [INFO] [stdout] 2771 | unchecked_mul!(u128, u128, unchecked_mul__u128, u128::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2772:13 [INFO] [stdout] | [INFO] [stdout] 2772 | unchecked_mul!(usize, u128, unchecked_mul__usize, usize::MAX); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` which comes from the expansion of the macro `unchecked_mul` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2813:13 [INFO] [stdout] | [INFO] [stdout] 2813 | default_contract!(wrapping_add__i128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> standard_contracts/src/foreign_contracts.rs:2814:13 [INFO] [stdout] | [INFO] [stdout] 2814 | default_contract!(wrapping_add__u128); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `result` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `result` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `result` which comes from the expansion of the macro `default_contract` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [WARN] too many lines in the log, truncating it