[gclist] write-barrier implementation in Java VM?

Sylvain Louboutin Sylvain.Louboutin@eng.sun.com
Wed, 8 Nov 2000 13:06:00 -0800 (PST)

>The overhead of incremental GC is typically that of
> a) write barrier code
> b) root scanning support
> c) incremental GC work
>while for a blocking GC, the overhead is only
> d) blocking GC work.

actually you may have to pay the price of a write barrier for
a stop-the-world approach as well:  e.g.,  you can imagine a
simple two space stop-the-world generational scheme where you'd
still need some form of write barrier to 'catch' intergenerational