harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Volosyuk" <ivan.volos...@gmail.com>
Subject Re: [DRLVM][GC] high-level design proposal for GCV5
Date Thu, 24 Aug 2006 13:54:41 GMT
> > It might also make sense to design in a write barrier verifier.  The
> > concept is to verify that all the old-to-young pointers are properly
> > handled.  One way of doing this is to force a full heap mark.  Then
> > compare the full heap mark's old-to-young pointers to what the write
> > barrier mechanism derived.
> This needs more thinking. The old-to-yound pointers got in a full-heap
> marking have only live ones. But I think the idea to have some write
> barrier verifier is interesting, e..g, the rememebered set has to be a
> superset of live old-to-yound pointers.

IMHO, write barrier verifier is a _must_ to have feature for us. The
same applies to full heap tracing-validation. As VM and JIT code are
subject of changes, it should be the way to isolate bugs introduced by
GC and the ones coming from VM/JIT.

> Thanks,
> xiaofeng

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message