On Wed, Feb 26, 2020 at 07:02 PM, Doug Wegscheid wrote:
Problem with getting more stack on-demand is that you are not guaranteed that your getmained storage is contiguous with your e during stack.
And that would be a nightmare and quite slow (each function call would have complex checks). Other option is to copy the old stack to the new space when resizing. Again hardly ideal as it fragments memory.
Traditionally on other simple/old platforms you would load your program in low memory address, have the head (dynamic memory) low as well, and put your stack to start at the top of memory working downwards (and hope they never met!). So actually for CMS we should go the same - but for small programs (e.g. cms subset) you would want the stack part of the program.?
Anyway we can have fun with options!
For?
