criticalsections are very fast / pooling mutexes / how does h ash-sync work?

Sun Dec 23 17:41:00 GMT 2001

"Boehm, Hans" <hans_boehm@hp.com> writes:
> I don't understand your concern about moving CriticalSections. The
> collector doesn't move anything. Why would the memory address change?

I'm sure the garbage collector doesn't (there's no way it could know
enough to do this properly), but I suspect that something in natObject
does; if I don't introduce the indirection, it crashes all over the
place. This could be my mistake; I'll double check it.
> I don't think it would be that difficult to port this to win32, and that may
> also be a way around some of these issues, since the fast path no longer
> involves any win32 calls.

Yes, it definately would be.
> You will have to add the appropriate compare-and-swap definition
> (natObject.cc), and supply a few other odds and ends.

Hrm, shouldn't the one that's there for Linux-x86 work? It's just
straight asm, no system calls...
Actually, it seems like it should "just work".. I'm going to give it a
try.
 - a