runtime: cleanup pagetrace

pagetrace functionality was removed with CL 583379.

Change-Id: I8e8718e6cf5415e326ec127fb294588866ee4e6a
Reviewed-on: https://go-review.googlesource.com/c/go/+/713260
Reviewed-by: Michael Knyszek <mknyszek@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: David Chase <drchase@google.com>

diff --git a/src/runtime/extern.go b/src/runtime/extern.go
index 62dab74bc0ccc3f167fe7e9958df2998ac4a2f89..c35aef06624f54df0682a788b5c57006188f07d1 100644 (file)
--- a/src/runtime/extern.go
+++ b/src/runtime/extern.go
@@ -171,13 +171,6 @@ It is a comma-separated list of name=val pairs setting these named variables:
        silently default to 1024. Future versions of Go may remove this limitation
        and extend profstackdepth to apply to the CPU profiler and execution tracer.
 
-       pagetrace: setting pagetrace=/path/to/file will write out a trace of page events
-       that can be viewed, analyzed, and visualized using the x/debug/cmd/pagetrace tool.
-       Build your program with GOEXPERIMENT=pagetrace to enable this functionality. Do not
-       enable this functionality if your program is a setuid binary as it introduces a security
-       risk in that scenario. Currently not supported on Windows, plan9 or js/wasm. Setting this
-       option for some applications can produce large traces, so use with care.
-
        panicnil: setting panicnil=1 disables the runtime error when calling panic with nil
        interface value or an untyped nil.