This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug ports/11291] potential deadlock in sem_*wait and sem_post for MIPS architectures
- From: "mischa dot jonker at viragelogic dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 17 Feb 2010 17:56:23 -0000
- Subject: [Bug ports/11291] potential deadlock in sem_*wait and sem_post for MIPS architectures
- References: <20100217150652.11291.mischa.jonker@viragelogic.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mischa dot jonker at viragelogic dot com 2010-02-17 17:56 -------
Indeed, the + is missing. This could cause statements after the macro to read a
value from before the macro (as the compiler doesn't expect the macro to change it
without the +, and therefore might use some old value stored in a register).
But this is all within the same thread/instance: it doesn't fix the problem. What
if a different thread changes isem->value?? The only way to tell the compiler
(that I know of I must say;-)) is by means of the 'volatile' keyword.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11291
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.