On Thursday, 23 January 2014 at 16:15:46 UTC, Frustrated wrote:
The point is that making the **STACK** TLS too should a way
around having to use synchronization.
Precisely because the STACK is not TLS makes functions not
thread
safe(since data is already "safe" in d).
Maybe you could elaborate a bit on where you see the problem
here? The claim that stack memory is not thread-local contradicts
commonly used terminology, since the execution stack is
intrinsically part of a single thread. In fact, from a user-space
perspective a context switch is little more than just switching
out the CPU registers, including the stack pointer, for a
different set.
David
