On Friday, 15 August 2014 at 20:17:51 UTC, Carl Sturtivant wrote:
On Friday, 15 August 2014 at 15:40:35 UTC, Sean Kelly wrote:
I thought it did, but apparently the behavior of VirtualAlloc
and mmap (which Fiber uses to allocate the stack) simply
reserves the range and then commits it lazily, even though
what you've told it to do is allocate the memory. This is
really great news since it means that no code changes will be
required to do the thing I wanted to do anyway.
Just read this after posting earlier replies! Very exciting.
I'll be doing some experiments to see how this works out.
What about at 32-bits?
I'm sure it works the same, but reserving large chunks of memory
there would eat up the address space. I think the default will
have to remain some reasonably low number on 32-bit.
