Public bug reported: Binary package hint: gcc-4.4
Observed in gcc 4.4.2-3ubuntu1 Believed to affect all versions __sync_synchronnize() should perform a memory barrier, but is a noop (at least with -O2) __sync_lock_release() should place a memory barrier before the compare-exchange operation, but actually puts the barrier after, which may cause unsafe spinlock release Implications: packages built with unfixed gcc which use these intrinsics may not be multicore-safe on armel. Upstream bug link and further information to follow shortly, when available. ** Affects: gcc-4.4 (Ubuntu) Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: armel armv7 ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs