mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-24 14:30:43 -08:00
Mps wiki trace: (tweak) .scan.loop.once
Copied from Perforce Change: 161481 ServerID: perforce.ravenbrook.com
This commit is contained in:
parent
58e1d0e56b
commit
59c81be6ab
1 changed files with 3 additions and 3 deletions
|
|
@ -63,13 +63,13 @@
|
|||
|
||||
<h3>.scan.loop:</h3>
|
||||
|
||||
<p>If the seg is full and non-white (eg. all grey) when scanning starts, then a single linear scan will make the seg non-grey (in fact: all black).</p>
|
||||
<p>.scan.loop.once: If the seg is full and non-white (eg. all grey) when scanning starts, then a single linear scan will make the seg non-grey (in fact: all black). In this case only, we do not need a loop.</p>
|
||||
|
||||
<p>Otherwise, there are two ways new grey objects can appear in the segment while we are scanning it:</p>
|
||||
|
||||
<p>.scan.loop.white: if the seg contains some white objects when we start a linear scan, then a Ref that points backwards into the same seg can fix and grey an object that was skipped as white when the linear scan passed over it. So scanning must loop until the whole seg is non-grey.</p>
|
||||
<p>.scan.loop.white: If the seg contains some white objects when we start a linear scan, then a Ref that points backwards into the same seg can fix and grey an object that was skipped as white when the linear scan passed over it. So scanning must loop until the whole seg is non-grey.</p>
|
||||
|
||||
<p>.scan.loop.buffer: if the seg is buffered, and the buffer is Forwarding-grey or Mutator-grey (not yet implemented), then new grey objects can arrive during the scan.</p>
|
||||
<p>.scan.loop.buffer: If the seg is buffered, and the buffer is Forwarding-grey or Mutator-grey (not yet implemented), then new grey objects can arrive during the scan.</p>
|
||||
|
||||
|
||||
<h3>.scan.total:</h3>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue