RSSA

[Matthew Fluet]

> > Why isn't the stack check for limit checks completely orthogonal to the
> > array/heap distinction?  An SSA function which begins with a variable
> > array allocation should be able to get by with one limit check for both
> > the array and the stack.
> 
> Agreed.  Should we add stackToo to the Array constructor?

I think so.

> In limit check insertion, that was (and will be) handled by adding to
> the bytesAllocated field, so the codegens don't need to do anything.
> Actually, the right amount to add is 3 words = 12 bytes.  And of
> course, LIMIT_SLOP comes in to play as always -- and will be handled
> by limit check insertion.

O.k.  Then that means I'll never see a case where extraBytes = 0.