You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I think it makes sense why AtomicI64, AtomicU64 are not available from the standard library for my target. I see that you have a crossbeam_no_atomic_64 cfg available, but I could not set it like:
crossbeam-utils = { version = "0.8", features = ["crossbeam_no_atomic_64"]}
// errors with:
// the package `testdep` depends on `crossbeam-utils`, with features: `crossbeam_no_atomic_64` but `crossbeam-utils` does not have these features.
Do you know a way I can make it compile where maximum atomic width is 32 bits?
The text was updated successfully, but these errors were encountered:
utsavm9
changed the title
Attempting to use more than max. atomic width
Attempting to use Atomics larger than max. atomic width
Aug 6, 2021
So, I think it makes sense why AtomicI64, AtomicU64 are not available from the standard library for my target. I see that you have a crossbeam_no_atomic_64 cfg available, but I could not set it like:
I am trying to compile
crossbeam-utils = "0.8"
for a non-unix target and I get this error:The target I am compiling to has
max_atomic_width: Some(32),
set similar to what it is here:https://github.com/rust-lang/rust/blob/e3231e35b6bbfabca1d9ceff9c4690af00328706/src/librustc_back/target/armv4t_unknown_linux_gnueabi.rs#L31
So, I think it makes sense why
AtomicI64, AtomicU64
are not available from the standard library for my target. I see that you have acrossbeam_no_atomic_64
cfg available, but I could not set it like:Do you know a way I can make it compile where maximum atomic width is 32 bits?
The text was updated successfully, but these errors were encountered: