Re: [rvm-research] MiscHeader and putfieldWriteBarrier

[Eliot M. <mo...@cs...>]

On 6/28/2010 8:32 PM, Robin Garner wrote:

> You also need to increase MiscHeaderConstants.NUM_BYTES_HEADER by the
> size of your header word.
> ...
> You can get around this (at least initially) by using a GC that doesn't
> require barriers, such as MarkSweep.

True, a non-moving collector avoids the barrier issue for
non-concurrent collectors, but you still need means to
trace the pointer, unless you have some other way to
guarantee that the referent is not collected away ....

But I think previous posts have addressed that.

Cheers -- Eliot Moss