Re: ROTOR GC

The lines that you marked in your email are, indeed, updates. But
remember that there are many places where other refs to the same object
may be hanging out - the finalization queue, the elder generation, and
the handle table, for example. The value of these refs need also to be
updated - in the case of other calls on copy_object_simple, it is done
immediately using GetRelocated. Otherwise, take a look at
get_copied_object (and Relocate, which uses it) to see the rest of the
relocation pass in action at the end of the copy_phase.

Hope this helps!

-- David

> -----Original Message-----
> From: Discussion of the Rotor Shared Source CLI
> implementation [mailto:[email protected]] On
> Behalf Of Pedro Felix
> Sent: Wednesday, June 18, 2003 4:51 AM
> To: [email protected]
> Subject: Re: [DOTNET-ROTOR] ROTOR GC
>
> It was only after seeing the code that I was
> confused because the "copy_object_simple" "seems" to fix-up
> the references already.