Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [5 earlier articles] |
| Re: Static Garbage Collection stock@esa.informatik.tu-darmstadt.de (Florian Stock) (2009-05-26) |
| Re: Static Garbage Collection ott@mirix.org (Matthias-Christian Ott) (2009-05-26) |
| Re: Static Garbage Collection vincent@famillebelliard.fr (Vincent Belliard) (2009-05-26) |
| Re: Static Garbage Collection DrDiettrich1@aol.com (Hans-Peter Diettrich) (2009-05-29) |
| Re: Static Garbage Collection armelasselin@hotmail.com (Armel) (2009-05-29) |
| Re: Static Garbage Collection marcov@stack.nl (Marco van de Voort) (2009-05-30) |
| Re: Static Garbage Collection vincent@famillebelliard.fr (Vincent Belliard) (2009-05-31) |
| Re: Static Garbage Collection armelasselin@hotmail.com (Armel) (2009-06-01) |
| From: | Vincent Belliard <vincent@famillebelliard.fr> |
| Newsgroups: | comp.compilers |
| Date: | 31 May 2009 21:58:29 GMT |
| Organization: | les newsgroups par Orange |
| References: | 09-05-120 09-05-130 09-05-135 |
| Keywords: | GC |
| Posted-Date: | 01 Jun 2009 10:21:41 EDT |
> note that garbage collection in multi-threaded application was proven to
> be possible using reference counts, even for cyclic graphs.
Yes, of course, it's possible to use references count in that case but it
needs extra data to search cycles and it cost a lot of CPU if you want to
release cycles as soon as they are not referenced anymore.
The use of qualified references avoid a lot of job even if it cost a
little bit more in data (because you must count references separately).
When an object has at least one reference from a local or global
variable, in no way it can be destroyed. In that case, when you release
one reference on the object you don't have extra job to do.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.