From 69e1711f287f5cd92296240f99d347edc23d40b7 Mon Sep 17 00:00:00 2001
From: Josh Bleecher Snyder <josh@tailscale.com>
Date: Mon, 7 Feb 2022 15:23:22 -0800
Subject: [PATCH] doc/go1.18: mention linker improvements

Change-Id: I12cad608448ddd17a5da2b1d1209007102d892a7
Reviewed-on: https://go-review.googlesource.com/c/go/+/383914
Trust: Josh Bleecher Snyder <josharian@gmail.com>
Run-TryBot: Josh Bleecher Snyder <josharian@gmail.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
---
 doc/go1.18.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/go1.18.html b/doc/go1.18.html
index 7e11f73820..ed32a93bc3 100644
--- a/doc/go1.18.html
+++ b/doc/go1.18.html
@@ -493,6 +493,14 @@ Do not send CLs removing the interior tags from such phrases.
 
 <h2 id="linker">Linker</h2>
 
+<p>
+  The linker emits <a href="https://tailscale.com/blog/go-linker/">far fewer relocations</a>.
+  As a result, most codebases will link faster, require less memory to link,
+  and generate smaller binaries.
+  Tools that process Go binaries should use Go 1.18's <code>debug/gosym</code> package
+  to transparently handle both old and new binaries.
+</p>
+
 <p><!-- CL 298610 -->
   The new linker <code>-asan</code> option supports the
   new <code>go</code> command <code>-asan</code> option.
-- 
2.50.0