Just to clear up some confusion:
On Windows, stack size is _not_ "virtually unlimited" - nor does Windows
support split stacks. Rather, each thread's stack occupies a contiguous
fixed block of address space. The only thing that's dynamic about it is
that only a small portion is initially backed by physical (or even
virtual) memory.
The per-thread stack size is configured at link time, and just happens
to be set to a humongously large size in the POV-Ray project.
Post a reply to this message
|