GC changes

[Bernd Schmidt]

On Mon, 15 Jan 2001, Jamie Lokier wrote:

> Mike Stump wrote:
> > > That is not safe.  You can't predict what kind of address arithmetic
> > > the compiler will make.  For example, strength reduction could cause
> > > a pointer to be pointing into the middle of an array, or worse,
> > > somewhere beyond it (incorporating some constant adjustments).
> >
> > We already need a switch to disable GC unfriendly optimizations.

Which ones would that be?
And how can we verify that the generated code is indeed GC friendly?  If it
can't be verified with a testsuite, such a switch might as well not be there,
since it won't work in practice.


Bernd