|garbage collection email@example.com (Lex Spoon) (2003-07-13)|
|Garbage collection firstname.lastname@example.org (2004-07-28)|
|Re: Garbage collection email@example.com (2004-08-04)|
|Re: Garbage collection firstname.lastname@example.org (Sebastian) (2004-08-04)|
|Re: Garbage collection email@example.com (2004-08-05)|
|Re: Garbage collection firstname.lastname@example.org (Basile Starynkevitch \[news\]) (2004-08-05)|
|Re: Garbage collection email@example.com (Nick Roberts) (2004-08-09)|
|Re: Garbage collection firstname.lastname@example.org (2004-08-10)|
|Re: Garbage collection email@example.com (glen herrmannsfeldt) (2004-08-11)|
|Re: Garbage collection firstname.lastname@example.org (Nick Roberts) (2004-08-13)|
|Re: Garbage collection email@example.com (Tomasz Zielonka) (2004-08-13)|
|[14 later articles]|
|From:||firstname.lastname@example.org (Michael Tiomkin)|
|Date:||5 Aug 2004 14:11:36 -0400|
email@example.com (William McCabe) wrote
> I am in the process of writing my own programming language and I would
> like to use garbage collection as a means for automatic memory
> management. I have decided that I want to implement a two-stage
> generational copying collector.
> I know how a copying and generational collector works but Im not sure
> how they work when put together. In my mind, generational is similar
> to coping in being that they both seperate the heap into two
> semi-spaces, but use totaly different methods to collect garbage. Can
> someone shed some light on this subject for me.
You can try to check what is done in Java, they use 4 generations
with different GC methods for different groups for one of their last
Notice that there is a problem with references from the "old"
objects to the "new" objects, these references need special treatment.
BTW, I'm not sure that GC is a part of a compiler, it's usually a
part of runtime support of a language.
[It's runtime, but it's often useful to tweak the compiler to generate
code that makes GC easier. -John]
Return to the
Search the comp.compilers archives again.