THE DESIGN OF THE GENERIC FIX FUNCTION design.mps.fix incomplete design richard 1995-08-25 INTRODUCTION: Fix is the interface through which the existence of references are communicated from the MPS client to the MPS. The interface also allows the value of such references to be changed (this is necessary in order to implement a moving memory manager). ARCHITECTURE: .contract: .protocol.was-marked: The ScanState has a Bool wasMarked field. This is used for finalization. .protocol.was-marked.set: All pool-specific fix methods must set the wasMarked field in the ScanState that they are passed. .protocol.was-marked.meaning: If the pool-specific fix method sets the wasMarked field to FALSE it is indicating the object referred to by the ref (the one that it is supposed to be fixing) has not previously been marked (ie, this is the first reference to this object that has been fixed), and that the object was white (in condemned space). .protocol.was-marked.conservative: It is always okay to set the wasMarked field to TRUE. .protocol.was-marked.finalizable: PoolMRG (design.mps.poolmrg) uses the value of the wasMarked field to determine whether an object is finalizable. IMPLEMENTATION: .fix.nailed: In a copying collection, a non-ambiguous fix to a broken heart should be snapped out _even if_ there is a RankAMBIG ref to same object (i.e., even if the broken heart is nailed); the RankAMBIG reference must either be stale (no longer in existence) or bogus.
2002-06-21 | RB | Converted from MMInfo database design document. |
This document is copyright © 1995-2002 Ravenbrook Limited. All rights reserved. This is an open source license. Contact Ravenbrook for commercial licensing options.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement, are disclaimed. In no event shall the copyright holders and contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
$Id: //info.ravenbrook.com/project/mps/branch/2013-05-01/keyword-arguments/design/fix/index.html#2 $
Ravenbrook / Projects / Memory Pool System / Master Product Sources / Design Documents