Dante Cannarozzi, Michael Plezbert, and Ron Cytron. Contaminated garbage collection. In Programming Languages Design and Implementation (PLDI), 2000. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Beltway: Getting Around Garbage Collection Gridlock - Blackburn, Jones, McKinley.. (2002) (11 citations) (Correct)
.... (MOS) collector handles older generations specially, bounding the volume copied at any collection and offering (eventual) completeness [24] Some regions may not be managed by a collector at all, either remaining uncollected [8] handled by static analysis [33] or via a stack like discipline [11, 18, 30]. We could combine Beltway with other collectors, but such exploration is beyond the scope of this paper. 6. Conclusion We present a new collector design, Beltway, that subsumes previous work on copying collectors. The generality of the Beltway framework enables the implementation of new copying ....
Dante Cannarozzi, Michael Plezbert, and Ron Cytron. Contaminated garbage collection. In Proceedings of the 2000.
Region-Based Memory Management for Real-Time Java - Beebee, Jr. (2001) (2 citations) (Correct)
....programs may cause memory leaks. If two threads share the same region, the region must be located at the top of the stack and live for the duration of the program [11] Contaminated garbage collection uses stacks of regions and dynamic region inference instead of static region inference [4]. An assignment of a eld of an object contained in a region with a longer lifetime to point to an object contained in a region with a shorter lifetime can cause the object allocated in the region with a shorter lifetime to be moved to the region with a longer lifetime. Thus, the assignment ....
....the region with a shorter lifetime to be moved to the region with a longer lifetime. Thus, the assignment contaminates the object by lifting it to a region higher on the stack. The garbage collector places objects accessable from multiple threads in a region with a lifetime of the entire program [4]. Our system has a need for a shared, recyclable memory accessible to multiple threads. We implement this memory by counting the number of times a thread enters 16 a memory area minus the number of times a thread exits a memory area. If this count is zero, our implementation deallocates the ....
D. Cannarozzi, M. Plezbert, and R. Cytron. Contaminated garbage collection. In PLDI [7].
Understanding the Connectivity of Heap Objects - Hirzel, Henkel, Diwan, Hind (2002) (2 citations) (Correct)
.... be performed automatically (for functional languages) based on a program analysis [38] or manually by the programmer [17] Contaminated garbage collection does a runtime analysis to track the lowest activation record (the one closest to the bottom of the stack) from which an object is reachable [8]. Objects are only collected when the activation record associated with them is popped. In some ways, this technique can be thought of as a runtime region analysis. If there is an ownership relation between two objects such that the owned object dies before the owner, and if the owned object has ....
D. Cannarozzi, M. Plezbert, and R. Cytron. Contaminated garbage collection. In Programming Languages Design and Implementation (PLDI), 2000.
Region-based Memory Management for Real-time Java - Higuera, Issarny, Banatre.. (2001) (Correct)
....cannot reference an object allocated in a scoped region. The above must be checked when executing instructions that store references within other objects (or arrays) which can be implemented by a region stack associated with each memory region, similarly to the contaminated collection solution [3]. We detail below how to support such a functionality: ffl When an object is created, it is associated with the scope of the active region. ffl The putfield (aputfield quick) instruction causes the object X to reference Y, whereas the aastore (aastore quick) instruction stores a reference Y ....
D. Cannarozzi, M. Plezbert, and R. Cytron. Contaminated Garbage Collection. In Proc. of the Conference on Programming Languages Design and Implementation (PLDI), volume 35, pages 264--273. ACM SIGPLAN, May 2000.
Effects Of Coalescing On The Performance Of Segregated Size.. - Defoe (2003) Self-citation (Cytron) (Correct)
No context found.
Dante J. Cannarozzi, Michael P. Plezbert, and Ron K. Cytron. Contaminated garbage collection. Proceedings of the ACM SIGPLAN '00 conference on Programming language design and implementation, pages 264--273, 2000.
Connectivity-Based Garbage Collection - Hirzel, Diwan, Hertz (2003) (2 citations) (Correct)
No context found.
Dante Cannarozzi, Michael Plezbert, and Ron Cytron. Contaminated garbage collection. In Programming Languages Design and Implementation (PLDI), 2000.
Framework for Analyzing Garbage Collection - Hertz, Immerman, Moss (2002) (Correct)
No context found.
Cannarozzi, D. J., Plezbert, M. P., and Cytron, R. K. Contaminated garbage collection. In Proceedings of SIGPLAN
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC