Problem with getting more stack on-demand is that you are not guaranteed that your getmained storage is contiguous with your e during stack.
If you have address space allocated for excess stack, do the excess pages of the stack end up in real memory immediately, or do they only exist in real memory once allocated?
On Wed, Feb 26, 2020 at 1:35 PM, Drew Derbyshire
<swhobbit@...> wrote:
On 2/26/20 3:20 AM,
rvjansen@... wrote:
> I see, and thanks for the explanation. Some thoughts: 32k words is quite a chunk for VM/370, but quite small for a serious program.
It's good for a 1972 IBM machine, but not good for even a 1985 24-bit
IBM machine; the LCML+L 4361 (a midrange machine at best) for example
has 12 Meg real, and by default users have a 4M virtual machine (and can
go higher).
> I would see the value of a macro approach to have a smaller initial stack, but to check size and getmain more if needed.
>
Even if it doesn't do dynamic allocation, I'm surprised it doesn't get
storage.? (I'd bypass getmain, that's OS emulation).
--
Drew Derbyshire
? Harris's Lament: All the good ones are taken
