>>where [1] is the area reserved for heap growth and [2] is the area
>>reserved for mmap()ed allocations.  now it looks like this:
>[...]
>>and as you can plainly, see, there is only one area now, [3], into
>>which either of them can grow.  this means (or will mean, ultimately),
>>that your heap can grow larger, or you can mmap() larger objects.
>
>Hurrah!  This is excellent news for ports with small amounts of VM, like
>acorn26.  I really must get around to swapping desks so I've got room to get
>an acorn26 machine running again...

yup.  i expect most platforms can find some benefit from this.

enjoy!

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."