[INFO] cloning repository https://github.com/dusk-phantom/duskphantom
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/dusk-phantom/duskphantom" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdusk-phantom%2Fduskphantom", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdusk-phantom%2Fduskphantom'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] c4d4a6194609e04df06386a0bcf34f1d326f7473
[INFO] checking dusk-phantom/duskphantom against 1ed2df61a19042f231709eb05d032ae9e2cb2084 for pr-160235
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdusk-phantom%2Fduskphantom" "/workspace/builds/worker-6-tc1/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-6-tc1/source'...
[INFO] [stderr] done.
[INFO] removed /workspace/builds/worker-6-tc1/source/rust-toolchain.toml
[INFO] started tweaking git repo https://github.com/dusk-phantom/duskphantom
[INFO] finished tweaking git repo https://github.com/dusk-phantom/duskphantom
[INFO] tweaked toml for git repo https://github.com/dusk-phantom/duskphantom written to /workspace/builds/worker-6-tc1/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/dusk-phantom/duskphantom on toolchain 1ed2df61a19042f231709eb05d032ae9e2cb2084
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1ed2df61a19042f231709eb05d032ae9e2cb2084" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/dusk-phantom/duskphantom 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" "+1ed2df61a19042f231709eb05d032ae9e2cb2084" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr] warning: crates/clang-front-back/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `clang-front-back` (manifest) generated 1 warning
[INFO] [stderr] warning: crates/duskphantom-backend/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-backend` (manifest) generated 1 warning
[INFO] [stderr] warning: crates/duskphantom-frontend/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-frontend` (manifest) generated 1 warning
[INFO] [stderr] warning: crates/duskphantom-middle/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-middle` (manifest) generated 1 warning
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded rustc-hash v2.0.0
[INFO] [stderr]   Downloaded similar v2.5.0
[INFO] [stderr]   Downloaded criterion-plot v0.4.5
[INFO] [stderr]   Downloaded insta v1.39.0
[INFO] [stderr]   Downloaded console v0.15.8
[INFO] [stderr]   Downloaded serde_cbor v0.11.2
[INFO] [stderr]   Downloaded llvm-sys v160.1.4
[INFO] [stderr]   Downloaded half v1.8.3
[INFO] [stderr]   Downloaded criterion v0.3.6
[INFO] [stderr]   Downloaded llvm-ir v0.11.1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,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" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:00c5645b54fe3ce5dae1417175e3c7fb6a6646c021d554ecd63a097b8b9f3602" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] 64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32
[INFO] running `Command { std: "docker" "start" "64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32" "/opt/rustwide/cargo-home/bin/cargo" "+1ed2df61a19042f231709eb05d032ae9e2cb2084" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-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" "-w" "/opt/rustwide/workdir" "--user" "0:0" "64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32" "/opt/rustwide/cargo-home/bin/cargo" "+1ed2df61a19042f231709eb05d032ae9e2cb2084" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stderr] warning: crates/clang-front-back/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `clang-front-back` (manifest) generated 1 warning
[INFO] [stderr] warning: crates/duskphantom-backend/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-backend` (manifest) generated 1 warning
[INFO] [stderr] warning: crates/duskphantom-frontend/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-frontend` (manifest) generated 1 warning
[INFO] [stderr] warning: crates/duskphantom-middle/Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-middle` (manifest) generated 1 warning
[INFO] [stderr]    Compiling proc-macro2 v1.0.85
[INFO] [stderr]    Compiling crossbeam-utils v0.8.20
[INFO] [stderr]     Checking typed-arena v2.0.2
[INFO] [stderr]     Checking either v1.12.0
[INFO] [stderr]     Checking diff v0.1.13
[INFO] [stderr]     Checking similar v2.5.0
[INFO] [stderr]     Checking hexf-parse v0.2.1
[INFO] [stderr]     Checking regex-automata v0.4.7
[INFO] [stderr]    Compiling semver v1.0.23
[INFO] [stderr]     Checking unsafe-libyaml v0.2.11
[INFO] [stderr]     Checking console v0.15.8
[INFO] [stderr]     Checking indexmap v2.2.6
[INFO] [stderr]    Compiling cc v1.0.99
[INFO] [stderr]    Compiling regex v1.10.5
[INFO] [stderr]     Checking bitflags v2.5.0
[INFO] [stderr]    Compiling rustix v0.38.34
[INFO] [stderr]    Compiling llvm-ir v0.11.1
[INFO] [stderr]     Checking linux-raw-sys v0.4.14
[INFO] [stderr]     Checking fastrand v2.1.0
[INFO] [stderr]     Checking log v0.4.21
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]     Checking duskphantom-utils v0.0.1 (/opt/rustwide/workdir/crates/duskphantom-utils)
[INFO] [stderr]    Compiling serde_json v1.0.117
[INFO] [stderr]     Checking rustc-hash v2.0.0
[INFO] [stderr]     Checking plotters-backend v0.3.6
[INFO] [stderr]     Checking textwrap v0.11.0
[INFO] [stderr]     Checking itertools v0.10.5
[INFO] [stderr]     Checking csv-core v0.1.11
[INFO] [stderr]     Checking half v1.8.3
[INFO] [stderr]     Checking clap v2.34.0
[INFO] [stderr]     Checking atty v0.2.14
[INFO] [stderr]    Compiling duskphantom v0.0.1 (/opt/rustwide/workdir)
[INFO] [stderr]     Checking byteorder v1.5.0
[INFO] [stderr]     Checking getrandom v0.2.15
[INFO] [stderr]     Checking plotters-svg v0.3.6
[INFO] [stderr]     Checking duskphantom-graph v0.0.2 (/opt/rustwide/workdir/crates/duskphantom-graph)
[INFO] [stderr]     Checking rand_core v0.6.4
[INFO] [stderr]    Compiling indoc v2.0.5
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-graph/src/lib.rs:103:18
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn nodes(&self) -> std::collections::hash_map::Values<u64, T> {
[INFO] [stdout]     |                  ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                  |
[INFO] [stdout]     |                  the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn nodes(&self) -> std::collections::hash_map::Values<'_, u64, T> {
[INFO] [stdout]     |                                                               +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-graph/src/lib.rs:107:17
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn iter(&self) -> UdGraphIter<T> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn iter(&self) -> UdGraphIter<'_, T> {
[INFO] [stdout]     |                                       +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Checking insta v1.39.0
[INFO] [stderr]     Checking crossbeam-epoch v0.9.18
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-graph/src/lib.rs:103:18
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn nodes(&self) -> std::collections::hash_map::Values<u64, T> {
[INFO] [stdout]     |                  ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                  |
[INFO] [stdout]     |                  the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn nodes(&self) -> std::collections::hash_map::Values<'_, u64, T> {
[INFO] [stdout]     |                                                               +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-graph/src/lib.rs:107:17
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn iter(&self) -> UdGraphIter<T> {
[INFO] [stdout]     |                 ^^^^^     ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                 |
[INFO] [stdout]     |                 the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn iter(&self) -> UdGraphIter<'_, T> {
[INFO] [stdout]     |                                       +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Checking crossbeam-deque v0.8.5
[INFO] [stderr]    Compiling llvm-sys v160.1.4
[INFO] [stderr]    Compiling quote v1.0.36
[INFO] [stderr]     Checking rayon-core v1.12.1
[INFO] [stderr]     Checking plotters v0.3.6
[INFO] [stderr]    Compiling syn v2.0.66
[INFO] [stderr]     Checking rayon v1.10.0
[INFO] [stderr]     Checking criterion-plot v0.4.5
[INFO] [stderr]     Checking tempfile v3.10.1
[INFO] [stderr]    Compiling serde_derive v1.0.203
[INFO] [stderr]    Compiling thiserror-impl v1.0.63
[INFO] [stderr]    Compiling clap_derive v4.5.13
[INFO] [stderr]    Compiling zerocopy-derive v0.7.35
[INFO] [stderr]     Checking zerocopy v0.7.35
[INFO] [stderr]     Checking thiserror v1.0.63
[INFO] [stderr]     Checking duskphantom-frontend v0.0.1 (/opt/rustwide/workdir/crates/duskphantom-frontend)
[INFO] [stderr]     Checking ppv-lite86 v0.2.20
[INFO] [stderr]     Checking rand_chacha v0.3.1
[INFO] [stderr]     Checking clap v4.5.13
[INFO] [stderr]     Checking rand v0.8.5
[INFO] [stderr]     Checking serde v1.0.203
[INFO] [stderr]     Checking serde_yaml v0.9.34+deprecated
[INFO] [stderr]     Checking csv v1.3.0
[INFO] [stderr]     Checking serde_cbor v0.11.2
[INFO] [stderr]     Checking tinytemplate v1.2.1
[INFO] [stderr]     Checking criterion v0.3.6
[INFO] [stderr]     Checking duskphantom-middle v0.0.1 (/opt/rustwide/workdir/crates/duskphantom-middle)
[INFO] [stderr]     Checking clang-front-back v0.0.1 (/opt/rustwide/workdir/crates/clang-front-back)
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:208:9
[INFO] [stdout]     |
[INFO] [stdout] 208 | /         cprintln!(
[INFO] [stdout] 209 | |             "[INFO] loop {} is made candidate {}!",
[INFO] [stdout] 210 | |             pre_header.name,
[INFO] [stdout] 211 | |             candidate.dump()
[INFO] [stdout] 212 | |         );
[INFO] [stdout]     | |_________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:176:13
[INFO] [stdout]     |
[INFO] [stdout] 176 |             cprintln!("[INFO] loop {} has multiple exit edges", pre_header.name);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:184:13
[INFO] [stdout]     |
[INFO] [stdout] 184 | /             cprintln!(
[INFO] [stdout] 185 | |                 "[INFO] loop {}'s pred is not {}",
[INFO] [stdout] 186 | |                 pre_header.name,
[INFO] [stdout] 187 | |                 pre_header.name
[INFO] [stdout] 188 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:194:13
[INFO] [stdout]     |
[INFO] [stdout] 194 |             cprintln!("[INFO] loop {} does not have indvar", pre_header.name);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:203:13
[INFO] [stdout]     |
[INFO] [stdout] 203 |             cprintln!("[INFO] loop {} has conflict effect", pre_header.name);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:465:9
[INFO] [stdout]     |
[INFO] [stdout] 465 | /         cprintln!(
[INFO] [stdout] 466 | |             "[INFO] failed to merge {} with {} (indvar = {})",
[INFO] [stdout] 467 | |             a.dump(),
[INFO] [stdout] 468 | |             b.dump(),
[INFO] [stdout] 469 | |             indvar
[INFO] [stdout] 470 | |         );
[INFO] [stdout]     | |_________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:546:13
[INFO] [stdout]     |
[INFO] [stdout] 546 | /             cprintln!(
[INFO] [stdout] 547 | |                 "[INFO] loop {} fails because {} is not br",
[INFO] [stdout] 548 | |                 pre_header.name,
[INFO] [stdout] 549 | |                 exit.gen_llvm_ir()
[INFO] [stdout] 550 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:564:13
[INFO] [stdout]     |
[INFO] [stdout] 564 | /             cprintln!(
[INFO] [stdout] 565 | |                 "[INFO] loop {} fails because {} has multiple preds",
[INFO] [stdout] 566 | |                 pre_header.name,
[INFO] [stdout] 567 | |                 exit_bb.name
[INFO] [stdout] 568 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:575:13
[INFO] [stdout]     |
[INFO] [stdout] 575 | /             cprintln!(
[INFO] [stdout] 576 | |                 "[INFO] loop {} fails because {}'s first operand is not inst",
[INFO] [stdout] 577 | |                 pre_header.name,
[INFO] [stdout] 578 | |                 exit.gen_llvm_ir()
[INFO] [stdout] 579 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:583:13
[INFO] [stdout]     |
[INFO] [stdout] 583 | /             cprintln!(
[INFO] [stdout] 584 | |                 "[INFO] loop {} fails because {} is not condition",
[INFO] [stdout] 585 | |                 pre_header.name,
[INFO] [stdout] 586 | |                 cond.gen_llvm_ir()
[INFO] [stdout] 587 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:592:13
[INFO] [stdout]     |
[INFO] [stdout] 592 | /             cprintln!(
[INFO] [stdout] 593 | |                 "[INFO] loop {} fails because {} is not slt",
[INFO] [stdout] 594 | |                 pre_header.name,
[INFO] [stdout] 595 | |                 cond.gen_llvm_ir()
[INFO] [stdout] 596 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:600:13
[INFO] [stdout]     |
[INFO] [stdout] 600 | /             cprintln!(
[INFO] [stdout] 601 | |                 "[INFO] loop {} fails because {}'s lhs is not inst",
[INFO] [stdout] 602 | |                 pre_header.name,
[INFO] [stdout] 603 | |                 cond.gen_llvm_ir()
[INFO] [stdout] 604 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:612:17
[INFO] [stdout]     |
[INFO] [stdout] 612 | /                 cprintln!(
[INFO] [stdout] 613 | |                     "[INFO] loop {} fails because {} is not calculated before loop",
[INFO] [stdout] 614 | |                     pre_header.name,
[INFO] [stdout] 615 | |                     inst.gen_llvm_ir()
[INFO] [stdout] 616 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:626:13
[INFO] [stdout]     |
[INFO] [stdout] 626 | /             cprintln!(
[INFO] [stdout] 627 | |                 "[INFO] loop {} fails because {} is not phi",
[INFO] [stdout] 628 | |                 pre_header.name,
[INFO] [stdout] 629 | |                 indvar.gen_llvm_ir()
[INFO] [stdout] 630 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:636:13
[INFO] [stdout]     |
[INFO] [stdout] 636 | /             cprintln!(
[INFO] [stdout] 637 | |                 "[INFO] loop {} fails because {}'s incoming value length is not 2",
[INFO] [stdout] 638 | |                 pre_header.name,
[INFO] [stdout] 639 | |                 indvar.gen_llvm_ir()
[INFO] [stdout] 640 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:646:13
[INFO] [stdout]     |
[INFO] [stdout] 646 | /             cprintln!(
[INFO] [stdout] 647 | |                 "[INFO] loop {} fails because {} is not pre_header",
[INFO] [stdout] 648 | |                 pre_header.name,
[INFO] [stdout] 649 | |                 inc[0].1.name.clone()
[INFO] [stdout] 650 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:654:13
[INFO] [stdout]     |
[INFO] [stdout] 654 | /             cprintln!(
[INFO] [stdout] 655 | |                 "[INFO] loop {} fails because {}'s second incoming value is not inst",
[INFO] [stdout] 656 | |                 pre_header.name,
[INFO] [stdout] 657 | |                 indvar.gen_llvm_ir()
[INFO] [stdout] 658 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:662:13
[INFO] [stdout]     |
[INFO] [stdout] 662 | /             cprintln!(
[INFO] [stdout] 663 | |                 "[INFO] loop {} fails because {} is not add",
[INFO] [stdout] 664 | |                 pre_header.name,
[INFO] [stdout] 665 | |                 next_val.gen_llvm_ir()
[INFO] [stdout] 666 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:670:13
[INFO] [stdout]     |
[INFO] [stdout] 670 | /             cprintln!(
[INFO] [stdout] 671 | |                 "[INFO] loop {} fails because {}'s second operand is not constant",
[INFO] [stdout] 672 | |                 pre_header.name,
[INFO] [stdout] 673 | |                 next_val.gen_llvm_ir()
[INFO] [stdout] 674 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:679:13
[INFO] [stdout]     |
[INFO] [stdout] 679 | /             cprintln!(
[INFO] [stdout] 680 | |                 "[INFO] loop {} fails because {} is not in loop",
[INFO] [stdout] 681 | |                 pre_header.name,
[INFO] [stdout] 682 | |                 next_bb.name
[INFO] [stdout] 683 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:688:17
[INFO] [stdout]     |
[INFO] [stdout] 688 | /                 cprintln!(
[INFO] [stdout] 689 | |                     "[INFO] loop {} fails because {} has multiple phi",
[INFO] [stdout] 690 | |                     pre_header.name,
[INFO] [stdout] 691 | |                     inst.gen_llvm_ir()
[INFO] [stdout] 692 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-middle/src/transform/mod.rs:58:9
[INFO] [stdout]    |
[INFO] [stdout] 58 | /         cprintln!(
[INFO] [stdout] 59 | |             "## Pass {} {}\n\nTime elapsed = {} µs\n\nDiff:\n\n```diff\n{}```\n",
[INFO] [stdout] 60 | |             Self::name(),
[INFO] [stdout] 61 | |             if changed { "[CHANGED]" } else { "" },
[INFO] [stdout] 62 | |             elapsed,
[INFO] [stdout] 63 | |             diff(&program_before, &program_after)
[INFO] [stdout] 64 | |         );
[INFO] [stdout]    | |_________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:208:9
[INFO] [stdout]     |
[INFO] [stdout] 208 | /         cprintln!(
[INFO] [stdout] 209 | |             "[INFO] loop {} is made candidate {}!",
[INFO] [stdout] 210 | |             pre_header.name,
[INFO] [stdout] 211 | |             candidate.dump()
[INFO] [stdout] 212 | |         );
[INFO] [stdout]     | |_________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:176:13
[INFO] [stdout]     |
[INFO] [stdout] 176 |             cprintln!("[INFO] loop {} has multiple exit edges", pre_header.name);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:184:13
[INFO] [stdout]     |
[INFO] [stdout] 184 | /             cprintln!(
[INFO] [stdout] 185 | |                 "[INFO] loop {}'s pred is not {}",
[INFO] [stdout] 186 | |                 pre_header.name,
[INFO] [stdout] 187 | |                 pre_header.name
[INFO] [stdout] 188 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:194:13
[INFO] [stdout]     |
[INFO] [stdout] 194 |             cprintln!("[INFO] loop {} does not have indvar", pre_header.name);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:203:13
[INFO] [stdout]     |
[INFO] [stdout] 203 |             cprintln!("[INFO] loop {} has conflict effect", pre_header.name);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:465:9
[INFO] [stdout]     |
[INFO] [stdout] 465 | /         cprintln!(
[INFO] [stdout] 466 | |             "[INFO] failed to merge {} with {} (indvar = {})",
[INFO] [stdout] 467 | |             a.dump(),
[INFO] [stdout] 468 | |             b.dump(),
[INFO] [stdout] 469 | |             indvar
[INFO] [stdout] 470 | |         );
[INFO] [stdout]     | |_________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:546:13
[INFO] [stdout]     |
[INFO] [stdout] 546 | /             cprintln!(
[INFO] [stdout] 547 | |                 "[INFO] loop {} fails because {} is not br",
[INFO] [stdout] 548 | |                 pre_header.name,
[INFO] [stdout] 549 | |                 exit.gen_llvm_ir()
[INFO] [stdout] 550 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:564:13
[INFO] [stdout]     |
[INFO] [stdout] 564 | /             cprintln!(
[INFO] [stdout] 565 | |                 "[INFO] loop {} fails because {} has multiple preds",
[INFO] [stdout] 566 | |                 pre_header.name,
[INFO] [stdout] 567 | |                 exit_bb.name
[INFO] [stdout] 568 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:575:13
[INFO] [stdout]     |
[INFO] [stdout] 575 | /             cprintln!(
[INFO] [stdout] 576 | |                 "[INFO] loop {} fails because {}'s first operand is not inst",
[INFO] [stdout] 577 | |                 pre_header.name,
[INFO] [stdout] 578 | |                 exit.gen_llvm_ir()
[INFO] [stdout] 579 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:583:13
[INFO] [stdout]     |
[INFO] [stdout] 583 | /             cprintln!(
[INFO] [stdout] 584 | |                 "[INFO] loop {} fails because {} is not condition",
[INFO] [stdout] 585 | |                 pre_header.name,
[INFO] [stdout] 586 | |                 cond.gen_llvm_ir()
[INFO] [stdout] 587 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:592:13
[INFO] [stdout]     |
[INFO] [stdout] 592 | /             cprintln!(
[INFO] [stdout] 593 | |                 "[INFO] loop {} fails because {} is not slt",
[INFO] [stdout] 594 | |                 pre_header.name,
[INFO] [stdout] 595 | |                 cond.gen_llvm_ir()
[INFO] [stdout] 596 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:600:13
[INFO] [stdout]     |
[INFO] [stdout] 600 | /             cprintln!(
[INFO] [stdout] 601 | |                 "[INFO] loop {} fails because {}'s lhs is not inst",
[INFO] [stdout] 602 | |                 pre_header.name,
[INFO] [stdout] 603 | |                 cond.gen_llvm_ir()
[INFO] [stdout] 604 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:612:17
[INFO] [stdout]     |
[INFO] [stdout] 612 | /                 cprintln!(
[INFO] [stdout] 613 | |                     "[INFO] loop {} fails because {} is not calculated before loop",
[INFO] [stdout] 614 | |                     pre_header.name,
[INFO] [stdout] 615 | |                     inst.gen_llvm_ir()
[INFO] [stdout] 616 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:626:13
[INFO] [stdout]     |
[INFO] [stdout] 626 | /             cprintln!(
[INFO] [stdout] 627 | |                 "[INFO] loop {} fails because {} is not phi",
[INFO] [stdout] 628 | |                 pre_header.name,
[INFO] [stdout] 629 | |                 indvar.gen_llvm_ir()
[INFO] [stdout] 630 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:636:13
[INFO] [stdout]     |
[INFO] [stdout] 636 | /             cprintln!(
[INFO] [stdout] 637 | |                 "[INFO] loop {} fails because {}'s incoming value length is not 2",
[INFO] [stdout] 638 | |                 pre_header.name,
[INFO] [stdout] 639 | |                 indvar.gen_llvm_ir()
[INFO] [stdout] 640 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:646:13
[INFO] [stdout]     |
[INFO] [stdout] 646 | /             cprintln!(
[INFO] [stdout] 647 | |                 "[INFO] loop {} fails because {} is not pre_header",
[INFO] [stdout] 648 | |                 pre_header.name,
[INFO] [stdout] 649 | |                 inc[0].1.name.clone()
[INFO] [stdout] 650 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:654:13
[INFO] [stdout]     |
[INFO] [stdout] 654 | /             cprintln!(
[INFO] [stdout] 655 | |                 "[INFO] loop {} fails because {}'s second incoming value is not inst",
[INFO] [stdout] 656 | |                 pre_header.name,
[INFO] [stdout] 657 | |                 indvar.gen_llvm_ir()
[INFO] [stdout] 658 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:662:13
[INFO] [stdout]     |
[INFO] [stdout] 662 | /             cprintln!(
[INFO] [stdout] 663 | |                 "[INFO] loop {} fails because {} is not add",
[INFO] [stdout] 664 | |                 pre_header.name,
[INFO] [stdout] 665 | |                 next_val.gen_llvm_ir()
[INFO] [stdout] 666 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:670:13
[INFO] [stdout]     |
[INFO] [stdout] 670 | /             cprintln!(
[INFO] [stdout] 671 | |                 "[INFO] loop {} fails because {}'s second operand is not constant",
[INFO] [stdout] 672 | |                 pre_header.name,
[INFO] [stdout] 673 | |                 next_val.gen_llvm_ir()
[INFO] [stdout] 674 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:679:13
[INFO] [stdout]     |
[INFO] [stdout] 679 | /             cprintln!(
[INFO] [stdout] 680 | |                 "[INFO] loop {} fails because {} is not in loop",
[INFO] [stdout] 681 | |                 pre_header.name,
[INFO] [stdout] 682 | |                 next_bb.name
[INFO] [stdout] 683 | |             );
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]    --> crates/duskphantom-middle/src/transform/make_parallel.rs:688:17
[INFO] [stdout]     |
[INFO] [stdout] 688 | /                 cprintln!(
[INFO] [stdout] 689 | |                     "[INFO] loop {} fails because {} has multiple phi",
[INFO] [stdout] 690 | |                     pre_header.name,
[INFO] [stdout] 691 | |                     inst.gen_llvm_ir()
[INFO] [stdout] 692 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-middle/src/transform/mod.rs:58:9
[INFO] [stdout]    |
[INFO] [stdout] 58 | /         cprintln!(
[INFO] [stdout] 59 | |             "## Pass {} {}\n\nTime elapsed = {} µs\n\nDiff:\n\n```diff\n{}```\n",
[INFO] [stdout] 60 | |             Self::name(),
[INFO] [stdout] 61 | |             if changed { "[CHANGED]" } else { "" },
[INFO] [stdout] 62 | |             elapsed,
[INFO] [stdout] 63 | |             diff(&program_before, &program_after)
[INFO] [stdout] 64 | |         );
[INFO] [stdout]    | |_________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `llvm-ir`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `cprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `cprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> crates/duskphantom-middle/src/irgen/function_kit.rs:76:9
[INFO] [stdout]    |
[INFO] [stdout] 76 |         &mut self,
[INFO] [stdout]    |         ^^^^^^^^^ the lifetime is elided here
[INFO] [stdout] ...
[INFO] [stdout] 80 |     ) -> FunctionKit {
[INFO] [stdout]    |          ^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 80 |     ) -> FunctionKit<'_> {
[INFO] [stdout]    |                     ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's named elsewhere is confusing
[INFO] [stdout]   --> crates/duskphantom-middle/src/transform/loop_simplify.rs:38:56
[INFO] [stdout]    |
[INFO] [stdout] 38 |     pub fn new(ir_builder: &'a mut IRBuilderWraper) -> LoopSimplifier {
[INFO] [stdout]    |                             --                         ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                             |
[INFO] [stdout]    |                             the lifetime is named here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: consistently use `'a`
[INFO] [stdout]    |
[INFO] [stdout] 38 |     pub fn new(ir_builder: &'a mut IRBuilderWraper) -> LoopSimplifier<'a> {
[INFO] [stdout]    |                                                                      ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> crates/duskphantom-middle/src/irgen/function_kit.rs:76:9
[INFO] [stdout]    |
[INFO] [stdout] 76 |         &mut self,
[INFO] [stdout]    |         ^^^^^^^^^ the lifetime is elided here
[INFO] [stdout] ...
[INFO] [stdout] 80 |     ) -> FunctionKit {
[INFO] [stdout]    |          ^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 80 |     ) -> FunctionKit<'_> {
[INFO] [stdout]    |                     ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's named elsewhere is confusing
[INFO] [stdout]   --> crates/duskphantom-middle/src/transform/loop_simplify.rs:38:56
[INFO] [stdout]    |
[INFO] [stdout] 38 |     pub fn new(ir_builder: &'a mut IRBuilderWraper) -> LoopSimplifier {
[INFO] [stdout]    |                             --                         ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                             |
[INFO] [stdout]    |                             the lifetime is named here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: consistently use `'a`
[INFO] [stdout]    |
[INFO] [stdout] 38 |     pub fn new(ir_builder: &'a mut IRBuilderWraper) -> LoopSimplifier<'a> {
[INFO] [stdout]    |                                                                      ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Checking duskphantom-backend v0.0.2 (/opt/rustwide/workdir/crates/duskphantom-backend)
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:33:9
[INFO] [stdout]    |
[INFO] [stdout] 33 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep.to_string());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:39:9
[INFO] [stdout]    |
[INFO] [stdout] 39 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare base:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:44:9
[INFO] [stdout]    |
[INFO] [stdout] 44 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare offset:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:52:9
[INFO] [stdout]    |
[INFO] [stdout] 52 |         fprintln!("log/build_gep_inst.log";'a';"\ngen:\n{}\n",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:29:9
[INFO] [stdout]    |
[INFO] [stdout] 29 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:38:9
[INFO] [stdout]    |
[INFO] [stdout] 38 |         fprintln!("log/build_gep_inst.log";'a';"ofst:{:?}",ofst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:63:9
[INFO] [stdout]    |
[INFO] [stdout] 63 |         fprintln!("log/build_gep_inst.log";'a';"base:{:?}", base);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:68:9
[INFO] [stdout]    |
[INFO] [stdout] 68 |         fprintln!("log/build_gep_inst.log";'a';"final:{:?}", dst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `crate::*`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/vars.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 | use crate::*;
[INFO] [stdout]    |     ^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/mod.rs:30:9
[INFO] [stdout]    |
[INFO] [stdout] 30 | pub use instruction::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^ the name `block` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 34 | pub use super::irs::*;
[INFO] [stdout]    |         ------------- but the name `block` in the type namespace is also re-exported here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(ambiguous_glob_reexports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:68:5
[INFO] [stdout]    |
[INFO] [stdout] 68 |     fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:71:9
[INFO] [stdout]    |
[INFO] [stdout] 71 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:82:5
[INFO] [stdout]    |
[INFO] [stdout] 82 |     fprintln!("log/before_inst_combine.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:92:5
[INFO] [stdout]    |
[INFO] [stdout] 92 |     fprintln!("log/after_inst_scheduling.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:95:5
[INFO] [stdout]    |
[INFO] [stdout] 95 |     fprintln!("log/after_reg_alloc.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:35:5
[INFO] [stdout]    |
[INFO] [stdout] 35 |     fprintln!("log/before_handle_unlegal_inst.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:41:5
[INFO] [stdout]    |
[INFO] [stdout] 41 |     fprintln!("log/before_phisicalize.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:45:5
[INFO] [stdout]    |
[INFO] [stdout] 45 |     fprintln!("log/phisicalize_func.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 |     fprintln!("log/handle_ra.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     fprintln!("log/handle_stack.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:65:5
[INFO] [stdout]    |
[INFO] [stdout] 65 |     fprintln!("log/handle_mem.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:69:5
[INFO] [stdout]    |
[INFO] [stdout] 69 |     fprintln!("log/handle_offset_overflows.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:33:9
[INFO] [stdout]    |
[INFO] [stdout] 33 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep.to_string());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:39:9
[INFO] [stdout]    |
[INFO] [stdout] 39 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare base:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:44:9
[INFO] [stdout]    |
[INFO] [stdout] 44 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare offset:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_llvm/build_inst/gep.rs:52:9
[INFO] [stdout]    |
[INFO] [stdout] 52 |         fprintln!("log/build_gep_inst.log";'a';"\ngen:\n{}\n",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:29:9
[INFO] [stdout]    |
[INFO] [stdout] 29 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:38:9
[INFO] [stdout]    |
[INFO] [stdout] 38 |         fprintln!("log/build_gep_inst.log";'a';"ofst:{:?}",ofst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:63:9
[INFO] [stdout]    |
[INFO] [stdout] 63 |         fprintln!("log/build_gep_inst.log";'a';"base:{:?}", base);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/instruction/gep.rs:68:9
[INFO] [stdout]    |
[INFO] [stdout] 68 |         fprintln!("log/build_gep_inst.log";'a';"final:{:?}", dst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `crate::*`
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/vars.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 | use crate::*;
[INFO] [stdout]    |     ^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> crates/duskphantom-backend/src/from/from_self/mod.rs:30:9
[INFO] [stdout]    |
[INFO] [stdout] 30 | pub use instruction::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^ the name `block` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 34 | pub use super::irs::*;
[INFO] [stdout]    |         ------------- but the name `block` in the type namespace is also re-exported here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(ambiguous_glob_reexports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:68:5
[INFO] [stdout]    |
[INFO] [stdout] 68 |     fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:71:9
[INFO] [stdout]    |
[INFO] [stdout] 71 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:82:5
[INFO] [stdout]    |
[INFO] [stdout] 82 |     fprintln!("log/before_inst_combine.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:92:5
[INFO] [stdout]    |
[INFO] [stdout] 92 |     fprintln!("log/after_inst_scheduling.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/optimize/mod.rs:95:5
[INFO] [stdout]    |
[INFO] [stdout] 95 |     fprintln!("log/after_reg_alloc.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:35:5
[INFO] [stdout]    |
[INFO] [stdout] 35 |     fprintln!("log/before_handle_unlegal_inst.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:41:5
[INFO] [stdout]    |
[INFO] [stdout] 41 |     fprintln!("log/before_phisicalize.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:45:5
[INFO] [stdout]    |
[INFO] [stdout] 45 |     fprintln!("log/phisicalize_func.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 |     fprintln!("log/handle_ra.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     fprintln!("log/handle_stack.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:65:5
[INFO] [stdout]    |
[INFO] [stdout] 65 |     fprintln!("log/handle_mem.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> crates/duskphantom-backend/src/phisicalize.rs:69:5
[INFO] [stdout]    |
[INFO] [stdout] 69 |     fprintln!("log/handle_offset_overflows.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-backend/src/irs/func.rs:155:21
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter {
[INFO] [stdout]     |                     ^^^^^     ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter<'_> {
[INFO] [stdout]     |                                     ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-backend/src/optimize/analysis/cfg.rs:100:26
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs, OutBBs)> {
[INFO] [stdout]     |                          ^^^^^             ^^^^^  ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                          |                 |
[INFO] [stdout]     |                          |                 the same lifetime is hidden here
[INFO] [stdout]     |                          the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs<'_>, OutBBs<'_>)> {
[INFO] [stdout]     |                                                 ++++        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `super::*`
[INFO] [stdout]   --> src/cli.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 | use super::*;
[INFO] [stdout]    |     ^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `clap::arg`
[INFO] [stdout]   --> src/lib.rs:35:5
[INFO] [stdout]    |
[INFO] [stdout] 35 | use clap::arg;
[INFO] [stdout]    |     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `super::*`
[INFO] [stdout]   --> src/cli.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 | use super::*;
[INFO] [stdout]    |     ^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `clap::arg`
[INFO] [stdout]   --> src/lib.rs:35:5
[INFO] [stdout]    |
[INFO] [stdout] 35 | use clap::arg;
[INFO] [stdout]    |     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-backend/src/irs/func.rs:155:21
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter {
[INFO] [stdout]     |                     ^^^^^     ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter<'_> {
[INFO] [stdout]     |                                     ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> crates/duskphantom-backend/src/optimize/analysis/cfg.rs:100:26
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs, OutBBs)> {
[INFO] [stdout]     |                          ^^^^^             ^^^^^  ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                          |                 |
[INFO] [stdout]     |                          |                 the same lifetime is hidden here
[INFO] [stdout]     |                          the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs<'_>, OutBBs<'_>)> {
[INFO] [stdout]     |                                                 ++++        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 29.46s
[INFO] running `Command { std: "docker" "inspect" "64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32", kill_on_drop: false }`
[INFO] [stdout] 64fb07b6b3426a3af05276b82f4ee549f04d1c38bddd179f01c15d7d541aee32
