Re: Storage management, was Compiler writers will love this language

lars@bearnip.com (Lars Duening)
17 Jul 2003 00:30:23 -0400

          From comp.compilers

Related articles
[11 earlier articles]
Re: Storage management, was Compiler writers will love this language mwotton@cse.unsw.edu.au (2003-07-04)
Re: Storage management, was Compiler writers will love this language blackmarlin@asean-mail.com (2003-07-04)
Re: Compiler writers will love this language ericmuttta@email.com (2003-07-15)
Re: Storage management, was Compiler writers will love this language stephen@dino.dnsalias.com (2003-07-17)
Re: Storage management, was Compiler writers will love this language monnier+comp.compilers/news/@cs-www.cs.yale.edu (Stefan Monnier) (2003-07-17)
Re: Storage management, was Compiler writers will love this language haberg@matematik.su.se (2003-07-17)
Re: Storage management, was Compiler writers will love this language lars@bearnip.com (2003-07-17)
Re: Storage management, was Compiler writers will love this language RLake@oxfam.org.pe (2003-07-17)
Re: Storage management, was Compiler writers will love this language dmr@bell-labs.com (Dennis Ritchie) (2003-07-17)
Re: Storage management, was Compiler writers will love this language dot@dotat.at (Tony Finch) (2003-07-17)
| List of all articles for this month |

From: lars@bearnip.com (Lars Duening)
Newsgroups: comp.compilers
Date: 17 Jul 2003 00:30:23 -0400
Organization: Compilers Central
References: 03-05-211 03-06-015 03-06-054 03-06-057 03-06-078 03-06-106 03-07-012 03-07-089
Keywords: storage, GC
Posted-Date: 17 Jul 2003 00:30:22 EDT

Eric <ericmuttta@email.com> wrote:


> I notice here, that you refer to "pure" reference-count GC, implying
> that some GC's are "hybrid" and combine reference-counting and some
> other scheme (supposeddly mark-and-sweep). How would such a hybrid GC
> work? any papers on the subject?


One way of doing this is to use reference counting as usual, but in
addition you keep track of all allocated memory. Every once in a while
you run a mark&sweep GC in the traditional way, using your list of
allocated memory to identify unreferenced memory blocks, and
recalculating the reference counts as you trace the referenced blocks.


Other hybrids are possible and limited only by your imagination (and the
application's requirements).


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.