Ivan, the problem is described in the example in H1682, I can add it to the email thread to invite other GC/JIT gurus to participate in the discussion.
The example: JIT has 2 references to report. Both of them point to the same object. JIT expects that both references are updated when GC moves object. 1) JIT reports reference 1 2) GC moves object and updates reference 1. 3) JIT reports reference 2, but the reference points to the old place where the object was. This is almost the same situation we have today. On 10/6/06, Ivan Volosyuk <[EMAIL PROTECTED]> wrote:
Why don't we update roots just when it was reported? Thus we don't need to keep large array of roots and it can also have positive influence on d-cache utilization (need to proof this).
-- Mikhail Fursov
