Ivan, there is no disagreement on the importance of those verifications (or validations) for Harmony GC. :-) What I was saying is we need more thinking on the design than the rough idea, such as when, how, what, etc.
Have you any good idea on the write barrier verfication design? Thanks, -xiaofeng On 8/24/06, Ivan Volosyuk <[EMAIL PROTECTED]> wrote:
> > 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. -- Ivan > > Thanks, > xiaofeng --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
