track the "owner" heap object in the ref write barrier

See the papers for reference counting with heap sliding views for details:
This commit is contained in:
Zahary Karadjov 2012-12-01 15:24:32 +02:00
commit e9e22ccb2a
4 changed files with 98 additions and 8 deletions

View file

@ -576,6 +576,9 @@ type
flags*: TLocFlags # location's flags
t*: PType # type of location
r*: PRope # rope value of location (code generators)
heapRoot*: PRope # keeps track of the enclosing heap object that
# owns this location (required by GC algorithms
# employing heap snapshots or sliding views)
a*: int # location's "address", i.e. slot for temporaries
# ---------------- end of backend information ------------------------------