From 6163cf87c8be3ecc11b9ab9d281c33b34d24aa47 Mon Sep 17 00:00:00 2001
From: Rob Pike <r@golang.org>
Date: Thu, 16 Jul 2015 14:45:46 +1000
Subject: [PATCH] doc: describe tracing, mention go fix

Also add a link to a couple of the talks from GopherCon 2015.

Change-Id: I11e1c550e999553163d3fb5e900f167c849ce33f
Reviewed-on: https://go-review.googlesource.com/12287
Reviewed-by: Andrew Gerrand <adg@golang.org>
---
 doc/go1.5.html | 25 +++++++++++++++++++++----
 1 file changed, 21 insertions(+), 4 deletions(-)

diff --git a/doc/go1.5.html b/doc/go1.5.html
index da1d05abce..7d0e6e357f 100644
--- a/doc/go1.5.html
+++ b/doc/go1.5.html
@@ -173,7 +173,8 @@ the drop in expected latency with the new collector may be important.
 </p>
 
 <p>
-Details of the new collector were presented in TODO: GopherCon talk.
+Details of the new collector were presented in a
+<a href="https://talks.golang.org/2015/go-gc.pdf">talk</a> at GopherCon 2015.
 </p>
 
 <h3 id="runtime">Runtime</h3>
@@ -531,11 +532,26 @@ more thorough validation of struct tags.
 
 <h3 id="trace_command">Trace command</h3>
 
+<p>
+A new tool is available for dynamic execution tracing of Go programs.
+The usage is analogous to how the test coverage tool works.
+Generation of traces is integrated into <code>go test</code>,
+and then a separate execution of the tracing tool itself analyzes the results:
+</p>
+
 <pre>
-TODO
-cmd/trace: new command to view traces (https://golang.org/cl/3601)
+$ go test -trace=trace.out path/to/package
+$ go tool trace [flags] pkg.test trace.out
 </pre>
 
+<p>
+The flags enable the output to be displayed in a browser window.
+For details, run <code>go tool trace -help</code>.
+There is also a description of the tracing facility in this
+<a href="https://talks.golang.org/2015/dynamic-tools.slide">talk</a>
+from GopherCon 2015.
+</p>
+
 <h3 id="doc_command">Go doc command</h3>
 
 <p>
@@ -928,7 +944,8 @@ the new <a href="/pkg/go/types/#Qualifier"><code>Qualifier</code></a>
 function type as an argument to several functions. This is an API change for
 the package, but since it is new to the core, it is not breaking the Go 1 compatibility
 rules since code that uses the package must explicitly ask for it at its new location.
-TODO: There should be a gofix for this.
+To update, run
+<a href="https://golang.org/cmd/go/#hdr-Run_go_tool_fix_on_packages"><code>go fix</code></a> on your package.
 </li>
 
 <li>
-- 
2.50.0