Excerpts from Kurt Stephens's message of Thu Jan 07 02:23:53 +0200 2010:
> Write barriers are expensive, it's *really* difficult to do unless your 
> compiler supports it.  I've toyed with using mprotect() to implement 
> write barriers, but signal handlers are just too slow.
> 
> I think LLVM has hooks for read and write barriers during JIT. Rubinious 
> might be good candidate for trying write barriers.  Write barriers could 
> enable single-threaded, real-time non-blocking treadmill style collection.

Rubinius already has a generational GC (which uses write
barriers.)


--
Magic is insufficiently advanced technology.