Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
RE: AW: [Caml-list] The tag bit
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2004-08-13 (14:58)
From: Ennals, Robert <robert.ennals@i...>
Subject: RE: AW: [Caml-list] The tag bit
Do mostly copying collectors actually solve the problem Andreas was

My impression was that mostly copying collectors are only really useful
when the vast majority of pointers are tagged. If all pointers into a
block are tagged, then the block is copied (just as it would be in a
copying collector); however if there are some ambiguous pointers into a
block (e.g. from within some C code you have linked to) then that block
is "pinned" into position, and must remain pinned until there are no
ambiguous pointers into it.

Thus, my impression was the mostly copying collection is great if one
has a language that uses tagged pointers, but wishes it to share GC-ed
objects with a language that doesn't understand tags, but that it
wouldn't really buy you anything in a situation where nothing was tagged
(which is what I think people were proposing).

Of course, I may be talking complete rubbish here - this isn't really my
field. Please feel free to tell me that I've completely misunderstood


> -----Original Message-----
> From: [mailto:owner-caml-
>] On Behalf Of T. Kurt Bond
> Sent: 13 August 2004 15:33
> To: Andreas Rossberg
> Cc:
> Subject: Re: AW: [Caml-list] The tag bit
> Andreas Rossberg writes:
> > AFAIK, a conservative collector is not allowed to move anything.
> > it is inherently incompatible with compacting and generational GC,
> > used in OCaml (and highly desirable).
> Joel F. Bartlett's 1988 paper "Compacting garbage collection with
> ambiguous roots" describes a conservative "mostly copying" compacting
> GC scheme; his 1989 paper "Mostly-Copying Garbage Collection Picks Up
> Generations and C++" descibes a generation variation.  Frederick Smith
> and Greg Morrisett's 1997 paper "Mostly-Copying Collection: A Viable
> Alternative to Conservative Mark-Sweep" describes an improved variant
> that they compared with the BDW by using both with the TIL/C ML
> compiler.  Giuseppe Attardi, Tito Flagella, and Pietro Iglio describe
> a GC in their 1998 paper "A Customisable Memory Management Framework
> for C++" that uses mostly copying GC for the default heap.
> --
> T. Kurt Bond,
> -------------------
> To unsubscribe, mail Archives:
> Bug reports: FAQ:
> Beginner's list:

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: