From: Rob Pike <r@golang.org>
Date: Fri, 28 Mar 2014 01:55:37 +0000 (+1100)
Subject: doc/go1.3.html: contiguous stacks
X-Git-Tag: go1.3beta1~244
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=610f395189528d5eb6a9dde36e39314403d0b7a3;p=gostls13.git

doc/go1.3.html: contiguous stacks

LGTM=bradfitz
R=golang-codereviews, bradfitz
CC=golang-codereviews
https://golang.org/cl/81650043
---

diff --git a/doc/go1.3.html b/doc/go1.3.html
index 60861fb547..770d0cc062 100644
--- a/doc/go1.3.html
+++ b/doc/go1.3.html
@@ -59,7 +59,14 @@ This is not a language change, just a clarification about an expected property o
 <h3 id="stacks">Stack</h3>
 
 <p>
-TODO stack copying, no longer segmented
+Go 1.3 has changed the implementation of goroutine stacks away from the old,
+"segmented" model to a contiguous model.
+When a goroutine needs more stack
+than is available, its stack is transferred to a larger single block of memory.
+The overhead of this transfer operation amortizes well and eliminates the old "hot spot"
+problem when a calculation repeatedly steps across a segment boundary.
+Details including performance numbers are in this
+<a href="http://golang.org/s/contigstacks">design document</a>.
 </p>
 
 <h3 id="stack_size">Stack size</h3>