known synchronized() failures?

Wed Apr 27 20:11:00 GMT 2005

Hi Bryce,
> There is a known bug in the synchronization implementation prior to
> GCC 4.0 - see PR 16662. Unfortunately that fix doesn't seem to have
> made it into the 3.4 branch.
> However, the symptoms of that problem are an 
> IllegalMonitorStateException - I'm not aware of any bugs that would 
> cause the symptoms you describe.
Interesting thread, as I use 3.4.3 and would want to make it "better".
So, actually I should grab the natObject.cc from CVS (or 1.31 at least), 
and then sync'ing should be at least as good as before.
I haven't seen any IllegalMonitorStateException yet, though, but I 
surely don't wanna have them comming when my application is out and 
running in the field.
However, I stumbled across one note Hans made in this patch:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libjava/java/lang/natObject.cc.diff?cvsroot=gcc&r1=1.30&r2=1.31
+	 // FIXME: Does this make sense on a uniprocessor, where
+	 // it actually yields? It's probably cheaper to convert.
I worry about the question about "making sense on a uniprocessor" - 
since this is where I'm targeted...
BR,
 Martin Egholm