[INFO] fetching crate cuda_std 0.2.2...
[INFO] testing cuda_std-0.2.2 against master#2fd6efc32704647e64d3d646d21c4c68eae100e4 for pr-149852-1
[INFO] extracting crate cuda_std 0.2.2 into /workspace/builds/worker-2-tc1/source
[INFO] started tweaking crates.io crate cuda_std 0.2.2
[INFO] finished tweaking crates.io crate cuda_std 0.2.2
[INFO] tweaked toml for crates.io crate cuda_std 0.2.2 written to /workspace/builds/worker-2-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate cuda_std 0.2.2 on toolchain 2fd6efc32704647e64d3d646d21c4c68eae100e4
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+2fd6efc32704647e64d3d646d21c4c68eae100e4" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+2fd6efc32704647e64d3d646d21c4c68eae100e4" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 16 packages to latest compatible versions
[INFO] [stderr]       Adding bitflags v1.3.2 (available: v2.10.0)
[INFO] [stderr]       Adding half v1.8.3 (available: v2.7.1)
[INFO] [stderr]       Adding vek v0.15.10 (available: v0.17.2)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+2fd6efc32704647e64d3d646d21c4c68eae100e4" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded num-integer v0.1.46
[INFO] [stderr]   Downloaded rustc_version v0.4.1
[INFO] [stderr]   Downloaded paste v1.0.15
[INFO] [stderr]   Downloaded cuda_std_macros v0.2.0
[INFO] [stderr]   Downloaded semver v1.0.27
[INFO] [stderr]   Downloaded half v1.8.3
[INFO] [stderr]   Downloaded approx v0.5.1
[INFO] [stderr]   Downloaded libm v0.2.15
[INFO] [stderr]   Downloaded vek v0.15.10
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:98afbf2d16093dec2546ff8915fddc74e65664aa03fc460b3712b1c2c54a33e4" "/opt/rustwide/cargo-home/bin/cargo" "+2fd6efc32704647e64d3d646d21c4c68eae100e4" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] ac55de0be0edabc11fb5e41ca4b699a7f967d382100d9b80797398fbf5068c9a
[INFO] running `Command { std: "docker" "start" "-a" "ac55de0be0edabc11fb5e41ca4b699a7f967d382100d9b80797398fbf5068c9a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "ac55de0be0edabc11fb5e41ca4b699a7f967d382100d9b80797398fbf5068c9a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "ac55de0be0edabc11fb5e41ca4b699a7f967d382100d9b80797398fbf5068c9a", kill_on_drop: false }`
[INFO] [stdout] ac55de0be0edabc11fb5e41ca4b699a7f967d382100d9b80797398fbf5068c9a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:98afbf2d16093dec2546ff8915fddc74e65664aa03fc460b3712b1c2c54a33e4" "/opt/rustwide/cargo-home/bin/cargo" "+2fd6efc32704647e64d3d646d21c4c68eae100e4" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 6854ba62a727b372f65b425f8fc2b47965b97d779b01b07db23b3e04106f9d70
[INFO] running `Command { std: "docker" "start" "-a" "6854ba62a727b372f65b425f8fc2b47965b97d779b01b07db23b3e04106f9d70", kill_on_drop: false }`
[INFO] [stderr]    Compiling autocfg v1.5.0
[INFO] [stderr]    Compiling libm v0.2.15
[INFO] [stderr]    Compiling proc-macro2 v1.0.105
[INFO] [stderr]    Compiling unicode-ident v1.0.22
[INFO] [stderr]    Compiling semver v1.0.27
[INFO] [stderr]    Compiling quote v1.0.43
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling paste v1.0.15
[INFO] [stderr]    Compiling half v1.8.3
[INFO] [stderr]    Compiling rustc_version v0.4.1
[INFO] [stderr]    Compiling bitflags v1.3.2
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]    Compiling vek v0.15.10
[INFO] [stderr]    Compiling num-integer v0.1.46
[INFO] [stderr]    Compiling approx v0.5.1
[INFO] [stderr]    Compiling cuda_std_macros v0.2.0
[INFO] [stderr]    Compiling cuda_std v0.2.2 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/lib.rs:79:11
[INFO] [stdout]    |
[INFO] [stdout] 79 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/lib.rs:87:11
[INFO] [stdout]    |
[INFO] [stdout] 87 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/float.rs:75:11
[INFO] [stdout]    |
[INFO] [stdout] 75 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/float.rs:57:23
[INFO] [stdout]    |
[INFO] [stdout] 57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 83 |         f32_intrinsic!(self, floor())
[INFO] [stdout]    |         ----------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/float.rs:59:19
[INFO] [stdout]    |
[INFO] [stdout] 59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 83 |         f32_intrinsic!(self, floor())
[INFO] [stdout]    |         ----------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/float.rs:57:23
[INFO] [stdout]    |
[INFO] [stdout] 57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 90 |         f32_intrinsic!(self, ceil())
[INFO] [stdout]    |         ---------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/float.rs:59:19
[INFO] [stdout]    |
[INFO] [stdout] 59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 90 |         f32_intrinsic!(self, ceil())
[INFO] [stdout]    |         ---------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/float.rs:57:23
[INFO] [stdout]    |
[INFO] [stdout] 57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]    |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 98 |         f32_intrinsic!(self, round())
[INFO] [stdout]    |         ----------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/float.rs:59:19
[INFO] [stdout]    |
[INFO] [stdout] 59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 98 |         f32_intrinsic!(self, round())
[INFO] [stdout]    |         ----------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 105 |         f32_intrinsic!(self, trunc())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 105 |         f32_intrinsic!(self, trunc())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:120:23
[INFO] [stdout]     |
[INFO] [stdout] 120 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:122:19
[INFO] [stdout]     |
[INFO] [stdout] 122 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 151 |         f32_intrinsic!(self, copysign(sign))
[INFO] [stdout]     |         ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 151 |         f32_intrinsic!(self, copysign(sign))
[INFO] [stdout]     |         ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:164:23
[INFO] [stdout]     |
[INFO] [stdout] 164 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:166:19
[INFO] [stdout]     |
[INFO] [stdout] 166 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 214 |         f32_intrinsic!(self, powi(n))
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 214 |         f32_intrinsic!(self, powi(n))
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:221:23
[INFO] [stdout]     |
[INFO] [stdout] 221 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:223:19
[INFO] [stdout]     |
[INFO] [stdout] 223 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 234 |         f32_intrinsic!(self, sqrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 234 |         f32_intrinsic!(self, sqrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 241 |         f32_intrinsic!(self, exp())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 241 |         f32_intrinsic!(self, exp())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 248 |         f32_intrinsic!(self, exp2())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 248 |         f32_intrinsic!(self, exp2())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:255:23
[INFO] [stdout]     |
[INFO] [stdout] 255 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:257:19
[INFO] [stdout]     |
[INFO] [stdout] 257 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 277 |         f32_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 277 |         f32_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 284 |         f32_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 284 |         f32_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 291 |         f32_intrinsic!(self, cbrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 291 |         f32_intrinsic!(self, cbrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 299 |         f32_intrinsic!(self, hypot(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 299 |         f32_intrinsic!(self, hypot(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 306 |         f32_intrinsic!(self, sin())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 306 |         f32_intrinsic!(self, sin())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 313 |         f32_intrinsic!(self, cos())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 313 |         f32_intrinsic!(self, cos())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 320 |         f32_intrinsic!(self, tan())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 320 |         f32_intrinsic!(self, tan())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 329 |         f32_intrinsic!(self, asin())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 329 |         f32_intrinsic!(self, asin())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 338 |         f32_intrinsic!(self, acos())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 338 |         f32_intrinsic!(self, acos())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 346 |         f32_intrinsic!(self, atan())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 346 |         f32_intrinsic!(self, atan())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 358 |         f32_intrinsic!(self, atan2(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 358 |         f32_intrinsic!(self, atan2(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:365:23
[INFO] [stdout]     |
[INFO] [stdout] 365 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:367:19
[INFO] [stdout]     |
[INFO] [stdout] 367 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:384:23
[INFO] [stdout]     |
[INFO] [stdout] 384 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:386:19
[INFO] [stdout]     |
[INFO] [stdout] 386 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:396:23
[INFO] [stdout]     |
[INFO] [stdout] 396 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:398:19
[INFO] [stdout]     |
[INFO] [stdout] 398 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 407 |         f32_intrinsic!(self, sinh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 407 |         f32_intrinsic!(self, sinh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 414 |         f32_intrinsic!(self, cosh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 414 |         f32_intrinsic!(self, cosh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 421 |         f32_intrinsic!(self, tanh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 421 |         f32_intrinsic!(self, tanh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 428 |         f32_intrinsic!(self, asinh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 428 |         f32_intrinsic!(self, asinh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 435 |         f32_intrinsic!(self, acosh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 435 |         f32_intrinsic!(self, acosh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:57:23
[INFO] [stdout]     |
[INFO] [stdout]  57 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 442 |         f32_intrinsic!(self, atanh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:59:19
[INFO] [stdout]     |
[INFO] [stdout]  59 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 442 |         f32_intrinsic!(self, atanh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f32_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 451 |         f64_intrinsic!(self, floor())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 451 |         f64_intrinsic!(self, floor())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 458 |         f64_intrinsic!(self, ceil())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 458 |         f64_intrinsic!(self, ceil())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 466 |         f64_intrinsic!(self, round())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 466 |         f64_intrinsic!(self, round())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 473 |         f64_intrinsic!(self, trunc())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 473 |         f64_intrinsic!(self, trunc())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:488:23
[INFO] [stdout]     |
[INFO] [stdout] 488 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:490:19
[INFO] [stdout]     |
[INFO] [stdout] 490 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 519 |         f64_intrinsic!(self, copysign(sign))
[INFO] [stdout]     |         ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 519 |         f64_intrinsic!(self, copysign(sign))
[INFO] [stdout]     |         ------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:532:23
[INFO] [stdout]     |
[INFO] [stdout] 532 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:534:19
[INFO] [stdout]     |
[INFO] [stdout] 534 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 582 |         f64_intrinsic!(self, powi(n))
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 582 |         f64_intrinsic!(self, powi(n))
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:589:23
[INFO] [stdout]     |
[INFO] [stdout] 589 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:591:19
[INFO] [stdout]     |
[INFO] [stdout] 591 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 602 |         f64_intrinsic!(self, sqrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 602 |         f64_intrinsic!(self, sqrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 609 |         f64_intrinsic!(self, exp())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 609 |         f64_intrinsic!(self, exp())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 616 |         f64_intrinsic!(self, exp2())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 616 |         f64_intrinsic!(self, exp2())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:623:23
[INFO] [stdout]     |
[INFO] [stdout] 623 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:625:19
[INFO] [stdout]     |
[INFO] [stdout] 625 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 645 |         f64_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 645 |         f64_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 652 |         f64_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 652 |         f64_intrinsic!(self, log10())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 659 |         f64_intrinsic!(self, cbrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 659 |         f64_intrinsic!(self, cbrt())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 667 |         f64_intrinsic!(self, hypot(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 667 |         f64_intrinsic!(self, hypot(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 674 |         f64_intrinsic!(self, sin())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 674 |         f64_intrinsic!(self, sin())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 681 |         f64_intrinsic!(self, cos())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 681 |         f64_intrinsic!(self, cos())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 688 |         f64_intrinsic!(self, tan())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 688 |         f64_intrinsic!(self, tan())
[INFO] [stdout]     |         --------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 697 |         f64_intrinsic!(self, asin())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 697 |         f64_intrinsic!(self, asin())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 706 |         f64_intrinsic!(self, acos())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 706 |         f64_intrinsic!(self, acos())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 714 |         f64_intrinsic!(self, atan())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 714 |         f64_intrinsic!(self, atan())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 726 |         f64_intrinsic!(self, atan2(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 726 |         f64_intrinsic!(self, atan2(other))
[INFO] [stdout]     |         ---------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:733:23
[INFO] [stdout]     |
[INFO] [stdout] 733 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:735:19
[INFO] [stdout]     |
[INFO] [stdout] 735 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:752:23
[INFO] [stdout]     |
[INFO] [stdout] 752 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:754:19
[INFO] [stdout]     |
[INFO] [stdout] 754 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:764:23
[INFO] [stdout]     |
[INFO] [stdout] 764 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:766:19
[INFO] [stdout]     |
[INFO] [stdout] 766 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 775 |         f64_intrinsic!(self, sinh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 775 |         f64_intrinsic!(self, sinh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 782 |         f64_intrinsic!(self, cosh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 782 |         f64_intrinsic!(self, cosh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 789 |         f64_intrinsic!(self, tanh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 789 |         f64_intrinsic!(self, tanh())
[INFO] [stdout]     |         ---------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 796 |         f64_intrinsic!(self, asinh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 796 |         f64_intrinsic!(self, asinh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 803 |         f64_intrinsic!(self, acosh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 803 |         f64_intrinsic!(self, acosh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:67:23
[INFO] [stdout]     |
[INFO] [stdout]  67 |         #[cfg(not(any(target_arch = "nvptx", target_arch = "nvptx64")))]
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 810 |         f64_intrinsic!(self, atanh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/float.rs:69:19
[INFO] [stdout]     |
[INFO] [stdout]  69 |         #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 810 |         f64_intrinsic!(self, atanh())
[INFO] [stdout]     |         ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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 `f64_intrinsic` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]  --> src/mem.rs:4:11
[INFO] [stdout]   |
[INFO] [stdout] 4 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]   |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]  --> src/mem.rs:6:11
[INFO] [stdout]   |
[INFO] [stdout] 6 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]   |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]  --> src/mem.rs:9:11
[INFO] [stdout]   |
[INFO] [stdout] 9 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]   |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/mem.rs:19:11
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/mem.rs:29:11
[INFO] [stdout]    |
[INFO] [stdout] 29 | #[cfg(any(target_arch = "nvptx", target_arch = "nvptx64"))]
[INFO] [stdout]    |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[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] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/mem.rs:35:1
[INFO] [stdout]    |
[INFO] [stdout] 35 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/mem.rs:53:1
[INFO] [stdout]    |
[INFO] [stdout] 53 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]  --> src/misc.rs:6:1
[INFO] [stdout]   |
[INFO] [stdout] 6 | #[gpu_only]
[INFO] [stdout]   | ^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]   = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/misc.rs:20:1
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/misc.rs:36:1
[INFO] [stdout]    |
[INFO] [stdout] 36 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]  --> src/atomic/intrinsics.rs:7:1
[INFO] [stdout]   |
[INFO] [stdout] 7 | #[gpu_only]
[INFO] [stdout]   | ^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]   = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:27:1
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:32:1
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:37:1
[INFO] [stdout]    |
[INFO] [stdout] 37 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:42:1
[INFO] [stdout]    |
[INFO] [stdout] 42 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]   --> src/atomic/intrinsics.rs:47:1
[INFO] [stdout]    |
[INFO] [stdout] 47 | #[gpu_only]
[INFO] [stdout]    | ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `gpu_only` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:66:17
[INFO] [stdout]     |
[INFO] [stdout]  66 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  83 | / load! {
[INFO] [stdout]  84 | |     relaxed, 32, device, gpu,
[INFO] [stdout]  85 | |     acquire, 32, device, gpu,
[INFO] [stdout]  86 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 106 | |     volatile, 64, system, sys,
[INFO] [stdout] 107 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `load` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:113:17
[INFO] [stdout]     |
[INFO] [stdout] 113 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 128 | / store! {
[INFO] [stdout] 129 | |     relaxed, 32, device, gpu,
[INFO] [stdout] 130 | |     release, 32, device, gpu,
[INFO] [stdout] 131 | |     volatile, 32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 151 | |     volatile, 64, system, sys,
[INFO] [stdout] 152 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `store` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]    --> src/atomic/intrinsics.rs:181:17
[INFO] [stdout]     |
[INFO] [stdout] 181 |                   #[$crate::gpu_only]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 211 | / atomic_fetch_op_2_reg! {
[INFO] [stdout] 212 | |     // inc (unsigned)
[INFO] [stdout] 213 | |
[INFO] [stdout] 214 | |     relaxed, inc, 32, u32, device, gpu,
[INFO] [stdout] ...   |
[INFO] [stdout] 362 | |     volatile, dec, 64, i64, system, sys,
[INFO] [stdout] 363 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_2_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `nvptx`
[INFO] [stdout]     --> src/atomic/intrinsics.rs:369:17
[INFO] [stdout]      |
[INFO] [stdout]  369 |                   #[$crate::gpu_only]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout]  400 | / atomic_fetch_op_3_reg! {
[INFO] [stdout]  401 | |     // and
[INFO] [stdout]  402 | |
[INFO] [stdout]  403 | |     relaxed, and, 32, u32, device, gpu,
[INFO] [stdout] ...    |
[INFO] [stdout] 1105 | |     volatile, exch, 64, f64, system, sys,
[INFO] [stdout] 1106 | | }
[INFO] [stdout]      | |_- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = note: expected values for `target_arch` are: `aarch64`, `amdgpu`, `arm`, `arm64ec`, `avr`, `bpf`, `csky`, `hexagon`, `loongarch32`, `loongarch64`, `m68k`, `mips`, `mips32r6`, `mips64`, `mips64r6`, `msp430`, `nvptx64`, `powerpc`, `powerpc64`, `riscv32`, `riscv64`, `s390x`, `sparc`, `sparc64`, `wasm32`, `wasm64`, `x86`, `x86_64`, and `xtensa`
[INFO] [stdout]      = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::gpu_only` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the attribute macro `$crate::gpu_only` may come from an old version of the `cuda_std_macros` crate, try updating your dependency with `cargo update -p cuda_std_macros`
[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 attribute macro `$crate::gpu_only` which comes from the expansion of the macro `atomic_fetch_op_3_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[WARN] too many lines in the log, truncating it
