Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| garbage collection lex@cc.gatech.edu (Lex Spoon) (2003-07-13) |
| Garbage collection wmccabe@hotmail.com (2004-07-28) |
| Re: Garbage collection nmm1@cus.cam.ac.uk (2004-08-04) |
| Re: Garbage collection sk@z.pl (Sebastian) (2004-08-04) |
| Re: Garbage collection tmk@netvision.net.il (2004-08-05) |
| Re: Garbage collection basile-news@starynkevitch.net (Basile Starynkevitch \[news\]) (2004-08-05) |
| Re: Garbage collection nick.roberts@acm.org (Nick Roberts) (2004-08-09) |
| Re: Garbage collection vbdis@aol.com (2004-08-10) |
| Re: Garbage collection gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-08-11) |
| Re: Garbage collection nick.roberts@acm.org (Nick Roberts) (2004-08-13) |
| [15 later articles] |
| From: | Sebastian <sk@z.pl> |
| Newsgroups: | comp.compilers |
| Date: | 4 Aug 2004 02:45:19 -0400 |
| Organization: | in Forma |
| References: | 04-07-085 |
| Keywords: | GC |
| Posted-Date: | 04 Aug 2004 02:45:19 EDT |
William McCabe wrote:
> I know how a copying and generational collector works but Im not sure
> how they work when put together. [snip] Can
> someone shield some light on this subject for me.
You can read the following 2-part article from MSDN. It quite nicely
explains how .Net garbage collector works -- it's also (partly*) copying &
generational collector at one (it even has 2 generations).
http://msdn.microsoft.com/msdnmag/issues/1100/GCI/
http://msdn.microsoft.com/msdnmag/issues/1200/GCI2/
*) it's copying GC for not too large objects (AFAIR less than 16KB), larger
objects are allocated from yet another heap and are unmoveable (as moving
large obiects to compact memory is too slow)
rgds
Sebastian Kaliszewski
--
"Never underestimate the power of human stupidity" -- from Notebooks of L.L.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.