Garbage collection Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section 10.4.3.

Slides:



Advertisements
Similar presentations
Garbage collection David Walker CS 320. Where are we? Last time: A survey of common garbage collection techniques –Manual memory management –Reference.
Advertisements

Introduction to Memory Management. 2 General Structure of Run-Time Memory.
Chapter 6 Data Types
Space Efficient Conservative Garbage Collection Hans-Juergen Boehm, Xerox PARC Presented by Ryan Braud.
PZ10B Programming Language design and Implementation -4th Edition Copyright©Prentice Hall, PZ10B - Garbage collection Programming Language Design.
Lecture 10: Heap Management CS 540 GMU Spring 2009.
Garbage Collection What is garbage and how can we deal with it?
Garbage Collection  records not reachable  reclaim to allow reuse  performed by runtime system (support programs linked with the compiled code) (support.
5. Memory Management From: Chapter 5, Modern Compiler Design, by Dick Grunt et al.
CS 326 Programming Languages, Concepts and Implementation Instructor: Mircea Nicolescu Lecture 18.
CPSC 388 – Compiler Design and Construction
CS 536 Spring Automatic Memory Management Lecture 24.
CSC321: Programming Languages 11-1 Programming Languages Tucker and Noonan Chapter 11: Memory Management 11.1 The Heap 11.2 Implementation of Dynamic Arrays.
Chapter 8 Runtime Support. How program structures are implemented in a computer memory? The evolution of programming language design has led to the creation.
Memory Management. History Run-time management of dynamic memory is a necessary activity for modern programming languages Lisp of the 1960’s was one of.
CS 1114: Data Structures – memory allocation Prof. Graeme Bailey (notes modified from Noah Snavely, Spring 2009)
PZ10A Programming Language design and Implementation -4th Edition Copyright©Prentice Hall, PZ10A - Heap storage Programming Language Design and.
Memory Allocation. Three kinds of memory Fixed memory Stack memory Heap memory.
12.5 Record Modifications Jayalakshmi Jagadeesan Id 106.
Chapter 10 Storage Management Implementation details beyond programmer’s control Storage/CPU time trade-off Binding times to storage.
The environment of the computation Declarations introduce names that denote entities. At execution-time, entities are bound to values or to locations:
Chapter 3.7 Memory and I/O Systems. 2 Memory Management Only applies to languages with explicit memory management (C or C++) Memory problems are one of.
Linked lists and memory allocation Prof. Noah Snavely CS1114
Reference Counters Associate a counter with each heap item Whenever a heap item is created, such as by a new or malloc instruction, initialize the counter.
UniProcessor Garbage Collection Techniques Paul R. Wilson University of Texas Presented By Naomi Sapir Tel-Aviv University.
Storage Management Lecture 12: Dolores Zage.
CS3012: Formal Languages and Compilers The Runtime Environment After the analysis phases are complete, the compiler must generate executable code. The.
Dynamic Memory Allocation Questions answered in this lecture: When is a stack appropriate? When is a heap? What are best-fit, first-fit, worst-fit, and.
Storage Management. The stack and the heap Dynamic storage allocation refers to allocating space for variables at run time Most modern languages support.
Basic Semantics Associating meaning with language entities.
1 Records Record aggregate of data elements –Possibly heterogeneous –Elements/slots are identified by names –Elements in same fixed order in all records.
11/26/2015IT 3271 Memory Management (Ch 14) n Dynamic memory allocation Language systems provide an important hidden player: Runtime memory manager – Activation.
1 Languages and Compilers (SProg og Oversættere) Heap allocation and Garbage Collection.
PZ10A Programming Language design and Implementation -4th Edition Copyright©Prentice Hall, Heap storage Dynamic allocation and stacks are generally.
Heap storage & Garbage collection Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001.
UniProcessor Garbage Collection Techniques Paul R. Wilson University of Texas Presented By Naomi Sapir Tel-Aviv University.
ISBN Chapter 6 Data Types Pointer Types Reference Types Memory Management.
University of Washington Wouldn’t it be nice… If we never had to free memory? Do you free objects in Java? 1.
Memory Management -Memory allocation -Garbage collection.
2/4/20161 GC16/3011 Functional Programming Lecture 20 Garbage Collection Techniques.
Smart Pointers. Dumb Pointers Pointers Necessary – Dynamic memory – Sharing memory.
CS412/413 Introduction to Compilers and Translators April 21, 1999 Lecture 30: Garbage collection.
Data Types Chapter 6: Data Types Lectures # 13. Topics Chapter 6: Data Types 2 Introduction Primitive Data Types Character String Types Array Types Associative.
Eliminating External Fragmentation in a Non-Moving Garbage Collector for Java Author: Fridtjof Siebert, CASES 2000 Michael Sallas Object-Oriented Languages.
CSC 533: Programming Languages Spring 2016
Storage Allocation Mechanisms
Garbage Collection What is garbage and how can we deal with it?
Lecture 6 of Computer Science II
Topic: Java Garbage Collection
CSC 533: Programming Languages Spring 2015
Storage 18-May-18.
Memory Management 6/20/ :27 PM
Dynamic Memory Allocation
Memory Management © 2004, D. J. Foreman.
Storage Management.
CS 153: Concepts of Compiler Design November 28 Class Meeting
Concepts of programming languages
CS Introduction to Operating Systems
PZ06C - Polymorphism Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section 7.3 PZ06C.
Strategies for automatic memory management
Activation records Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section
Heap storage & Garbage collection
List Allocation and Garbage Collection
List Allocation and Garbage Collection
C H A P T E R F I V E Memory Management.
Heap storage & Garbage collection
Automating Memory Management
CSC 533: Programming Languages Spring 2019
Activation records Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section
Garbage Collection What is garbage and how can we deal with it?
Presentation transcript:

Garbage collection Programming Language Design and Implementation (4th Edition) by T. Pratt and M. Zelkowitz Prentice Hall, 2001 Section 10.4.3

Garbage collection goal Process to reclaim memory.(Solve Fragmentation problem.) Algorithm: You can do garbage collection if you know where every pointer is in a program. If you move the allocated storage, simply change the pointer to it. This is true in LISP, ML, Java, Prolog Not true in C, C++, Pascal, Ada Garbage collection

Garbage collection: Mark-sweep algorithm First assume fixed size blocks of size k. (Later blocks of size n*k.) This is the LISP case. Two simple algorithms follow. (This is only an introduction to this topic. Many other algorithms exist) Algorithm 1: Fixed size blocks; Two pass mark-sweep algorithm: 1. Keep a linked list (free list) of objects available to be allocated. 2. Allocate objects on demand. 3. Ignore free commands. 4. When out of space, perform garbage collection: Pass 1. Mark every object still allocated. Pass 2. Every unmarked objects added to free list of available blocks. Garbage collection

Heap storage errors Error conditions: Dangling reference - Cannot occur. Each valid reference will be marked during sweep pass 1. Inaccessible storage - Will be reclaimed during sweep pass 2. Fragmentation - Does not occur; fixed size objects. Garbage collection

Garbage collection: reference counts Algorithm 2: 1. Associate a reference counter field, initially 0, with every allocated object. 2. Each time a pointer is set to an object, up the reference counter by 1. 3. Each time a pointer no longer points to an object, decrease the reference counter by 1. 4. If reference counter ever is to 0, then free object. Error conditions: Dangling reference - Cannot occur. Reference count is 0 only when nothing points to it. Fragmentation - Cannot occur. All objects are fixed size. Inaccessible storage - Can still occur, but not easily. Garbage collection

Memory compaction: Variable-size elements With variable sized blocks, the previous two algorithms will not work. In the left heap below, a block of size 3 cannot be allocated, even though 7 blocks are free. If the allocated blocks are moved to the start of the heap (compaction) and the free blocks collected, then a block of size up to 7 can be allocated. Garbage collection

Compaction algorithm For variable sized blocks, in pass 2 of the mark-sweep algorithm:  Move blocks to top of storage  Need to reset pointers that point to the old storage location to now point to the new storage. How to do this? Use tombstones and two storage areas, an A area and a B area: 1. Fill area A. 2. When A fills, do mark-sweep algorithm. 3. Move all allocated storage to start of B area. Leave marker in A area so other pointers pointing to this object can be modified. 4. After everything moved, area A can discarded. Allocate in B and later compact from B back to A. Garbage collection

Compaction algorithm (continued) Garbage collection

In place compaction Garbage collection