From 3a6a41868eb620912235f2dd3f9738c76035e731 Mon Sep 17 00:00:00 2001
From: Russ Cox <rsc@golang.org>
Date: Fri, 27 May 2016 16:30:03 -0400
Subject: [PATCH] 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>
---
 doc/go1.7.html | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/doc/go1.7.html b/doc/go1.7.html
index 46c575452f..e9f30d70cd 100644
--- a/doc/go1.7.html
+++ b/doc/go1.7.html
@@ -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>
-- 
2.51.0