Odd... I sent this to the ML a couple of weeks ago, but it doesn't seem to
have made it out...
I didn't see anything... I was hoping the silence meant you'd solved
the problem. :)
One suggestion I've got for you is that the gc-lock is a "special
case" lock, with some gross special case
Patrick Tullmann writes:
This would happen if the atomic test+set operations aren't defined or
aren't actually atomic. Kaffe falls back on a ?: operator in that
case...
Maybe kaffe should just #error out the compilation in this case..?
-Archie
