https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114103
--- Comment #4 from dave.anglin at bell dot net --- On 2024-02-26 5:54 a.m., redi at gcc dot gnu.org wrote: > I assume the problem is that the ATOMIC_xxx_LOCK_FREE macros have value 1 not > 2, so they're not unconditionally lock-free. > > Are any of the atomic integer types always lock-free for this target? No. The only "lock free" operations are load and clear word/double word. On linux, we fudge the support in the kernel where we can disable interrupts but the operation still can spin.
