What    |Removed                     |Added
                 CC|                            |

--- Comment #2 from 2010-08-15 18:56:24 PDT ---
Generally the GC should only scan data for which at least hasPointers() returns
true, and that isn't logically constant (e.g. TypeInfo instances, even though
they can contain pointers/references).

Maybe implementation would be simplest by adding a a pointer range to
ModuleInfo, that tells the GC what exactly should be scanned. Ideally, static
variables for which hasPointers() is false would not be included in this range.
This should drastically reduce the amount of data needed to be scanned by the
GC, because the C data segment is not included.

An extended implementation could accompany the pointer range with a precise
pointer map.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to