projects / platform / upstream / glib.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f20ae7f) | patch
gthread-posix: always use atomic pointer ops
authorRyan Lortie <desrt@desrt.ca>
Mon, 29 Oct 2012 09:13:40 +0000 (10:13 +0100)
committerRyan Lortie <desrt@desrt.ca>
Mon, 29 Oct 2012 15:18:10 +0000 (16:18 +0100)
commit311e18abdded1f525725ea6e2c346fb402b2af02
treedaeb32a27ae101fd080e5ce3d42cee3ce9365cddtree | snapshot
parentf20ae7fcfdaf9adeac3f73242adb798f1a80ddffcommit | diff
gthread-posix: always use atomic pointer ops

On platforms where dependent loads can be reordered (alpha) and we have
exotic implementation of pthread_mutex_lock() it could be possible that
our implementation of g_mutex_lock() is unsafe.

Always use atomic operations to avoid this possibility.

https://bugzilla.gnome.org/show_bug.cgi?id=686191
glib/gthread-posix.c diff | blob | history
Domain: System / Base;