This issue is both unnoticeable and surprising. It is not possible to know when and where this issue will occur. It will only occur in code that uses crossbeam-utils and fetch_* methods. This issue has been fixed in crossbeam-utils 0.8.7. Crates using `fetch_*` methods with `AtomicCell{i,u}64>` are affected by this issue. 32-bit targets without `Atomic{I,U}64` and 64-bit targets are not affected by this issue. This has been fixed in crossbeam-utils 0.8.7. There are currently no known workarounds.

0.8.6 - February 25, 2019 Resolves: There are currently no known workarounds. This issue is both unnoticeable and surprising. It is not possible to know when and where this issue will occur. It will only occur in code that uses crossbeam-utils and fetch_* methods. This issue has been fixed in crossbeam-utils 0.8.6. Crates using `fetch_*` methods with `AtomicCell{i,u}64>` are affected by this issue. 32-bit targets without `Atomic{I,U}64` and 64-bit targets are not affected by this issue. This has been fixed in crossbeam-utils 0.8.6. There are currently no known workar

0.8.5 - February 11, 2019 Resolves: This issue is both unnoticeable and surprising

. It is not possible to know when and where this issue will occur. It will only occur in code that uses crossbeam-utils and fetch_* methods. This issue has been fixed in crossbeam-utils 0.8.5. Crates using `fetch_*` methods with `AtomicCell{i,u}64>` are affected by this issue. 32-bit targets without `Atomic{I,U}64` and 64-bit targets are not affected by this issue. This has been fixed in crossbeam-utils 0.8.5. There are currently no known workarounds

What is this issue?

This issue is both unnoticeable and surprising. It is not possible to know when and where this issue will occur. It will only occur in code that uses crossbeam-utils and fetch_* methods. This issue has been fixed in crossbeam-utils 0.8.6. Crates using `fetch_*` methods with `AtomicCell{i,u}64>` are affected by this issue. 32-bit targets without `Atomic{I,U}64` and 64-bit targets are not affected by this issue. This has been fixed in crossbeam-utils 0.8.6. There are currently no known workarounds

Timeline

Published on: 02/15/2022 19:15:00 UTC
Last modified on: 06/09/2022 16:15:00 UTC

References