mirror of https://github.com/golang/go.git
doc: mention frame pointers in Go 1.7 release notes
For #15840. Change-Id: I2ecf5c7b00afc2034cf3d7a1fd78636a908beb67 Reviewed-on: https://go-review.googlesource.com/23517 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
This commit is contained in:
parent
496cf215cf
commit
3a6a41868e
|
|
@ -185,6 +185,17 @@ built with Go 1.6,
|
|||
sometimes by as much as 20-30%.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
On x86-64 systems, Go programs now maintain stack frame pointers
|
||||
as expected by profiling tools like Linux's perf and Intel's VTune,
|
||||
making it easier to analyze and optimize Go programs using these tools.
|
||||
The frame pointer maintenance has a small run-time overhead that varies
|
||||
but averages around 2%. We hope to reduce this cost in future releases.
|
||||
To build a toolchain that does not use frame pointers, set
|
||||
<code>GOEXPERIMENT=noframepointer</code> when running
|
||||
<code>make.bash</code>, <code>make.bat</code>, or <code>make.rc</code>.
|
||||
</p>
|
||||
|
||||
<h3 id="cmd/cgo">Cgo</h3>
|
||||
|
||||
<p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue