Re: Generational GC: what to do when older generation overflows?

How we deal with these issues is to make sure that there is always enough
room to copy all the objects in the heap. As the older generataion grow,
this may imply shrinking the amount of space you're allowed to use in the
nursery.

Note also that if objects have differeing alignmentr constraints, when
copied a group of object make take a little _more_ space than they did
originally (or a little less), so we include a "fudge factor" for that as
well. Of course at some point you must either grow the heap or declare "out
of space", but the latter will not happen during collection if you always
make sure that you have not quite filled half your space (when using a
copying collector).

Best wishes -- Eliot Moss
==============================================================================
J. Eliot B. Moss, Associate Professor     http://www.cs.umass.edu/~moss    www
Director, Arch. and Lang. Impl. Lab.      +1-413-545-4206                voice
Department of Computer Science            +1-413-695-4226                 cell
140 Governor's Drive, Room 372            +1-413-545-1249                  fax
University of Massachusetts at Amherst    [email protected]              email
Amherst, MA  01003-9264  USA              +1-413-545-3733 Priscilla Coe  sec'y
==============================================================================