Home | History | Annotate | Download | only in docs

Lines Matching full:heap

41     <li><a href="#barriers">Reading and writing references in the heap</a>
67 <li><a href="#gcdescriptors">Tracing GC pointers from heap
90 having to know the lifetimes of heap objects, making software easier to produce
111 machine is a pointer, it cannot move live objects in the heap (preventing the
170 <li>Write barriers when storing object references to the heap. These are
185 the runtime. These are used to crawl the heap for object
213 heap.<ol>
220 within heap objects.</li>
326 /// might copy them to another heap or generation.
430 variable references an object on the heap and is to be tracked for garbage
436 which a pointers into the GC heap.</p>
448 <p>The <tt>%metadata</tt> argument can be used to avoid requiring heap objects
496 <a name="barriers">Reading and writing references in the heap</a>
503 of a heap object. The code fragments inserted at these points are called
603 <p>This is not the appropriate place to implement a garbage collected heap or a
922 <dd>When the heap is exhausted, the collector marks reachable objects starting
927 heap area to another, compacting them in the process. Copying collectors
933 mature heap is compacting), but bring the added complexity of requiring