Test

Wed Sep 16 12:19:00 GMT 1998

>> I want compiler-supported precise gc, with support for write barriers
> if generational gc is configured. However, first we want to get
> a working base system working.

 I see. So, would that then be similar to [1]?
Then, let me ask the natural follow-up question as to how you're 
intending to handle multiple threads? Specifically, is it correct
that garbage collection will only be possible at certain gc points
(for which the compiler creates the precise information), and if that
is so, what is your strategy about rolling threads that have not reached
a gc point forward or backward to a gc point if a collection needs
to happen?
Or, alternatively, do you exclude preemptive threading --- where this
wouldn't be a problem because you could place preemption points where
gc points are? I remember reading that your run-time uses a cooperative
threading system; but isn't there value in having preemptive threads?
	- Godmar
[1] Amer Diwan and Eliot Moss and Richard Hudson
Compiler Support for Garbage Collection in a Statically Typed Language,
PLDI June 1992, Las Vegas, NV; pages 273--282