diff options
| author | Austin Clements <austin@google.com> | 2015-05-20 15:29:53 -0400 |
|---|---|---|
| committer | Austin Clements <austin@google.com> | 2015-06-02 19:57:50 +0000 |
| commit | e610c25df05246efa807e4724a9b2b0d00847604 (patch) | |
| tree | bbbc40e34a0b17648c0f975bba8bcbf9f76af069 /src/runtime/stack_test.go | |
| parent | c02b8911d84662ff6d0745acba6f2fcb79cc5cd1 (diff) | |
| download | go-e610c25df05246efa807e4724a9b2b0d00847604.tar.xz | |
runtime: decouple stack bounds and stack allocation size
Currently the runtime assumes that the allocation for the stack is
exactly [stack.lo, stack.hi). We're about to steal a small part of
this allocation for per-stack GC metadata. To prepare for this, this
commit adds a field to the G for the allocated size of the stack.
With this change, stack.lo and stack.hi continue to act as the true
bounds on the stack, but are no longer also used as the bounds on the
stack allocation.
(I also tried this the other way around, where stack.lo and stack.hi
remained the allocation bounds and I introduced a new top of stack.
However, there are far more places that assume stack.hi is the true
top of the stack than there are places that assume it's the top of the
allocation.)
Change-Id: Ifa9d956753be53d286d09cbc73d47fb34a18c0c6
Reviewed-on: https://go-review.googlesource.com/10312
Reviewed-by: Russ Cox <rsc@golang.org>
Diffstat (limited to 'src/runtime/stack_test.go')
0 files changed, 0 insertions, 0 deletions