[dev.boringcrypto] all: merge go1.9 into dev.boringcrypto

Previously we were at Go 1.9 rc2.

Change-Id: I9bea028d7078676b0f1f1408e45e7e1d5e349d23

doc/contrib.html

@@ -34,6 +34,7 @@ <h3 id="release"><a href="/doc/devel/release.html">Release History</a></h3>
 <p>A <a href="/doc/devel/release.html">summary</a> of the changes between Go releases. Notes for the major releases:</p>
 
 <ul>
+	<li><a href="/doc/go1.9">Go 1.9</a> <small>(August 2017)</small></li>
 	<li><a href="/doc/go1.8">Go 1.8</a> <small>(February 2017)</small></li>
 	<li><a href="/doc/go1.7">Go 1.7</a> <small>(August 2016)</small></li>
 	<li><a href="/doc/go1.6">Go 1.6</a> <small>(February 2016)</small></li>

doc/devel/release.html

@@ -20,7 +20,14 @@ <h2 id="policy">Release Policy</h2>
 and Go 1.9 is supported until Go 1.11 is released.
 We fix critical problems, including <a href="/security">critical security problems</a>,
 in supported releases as needed by issuing minor revisions
-(for example, Go 1.8.1, Go 1.8.2, and so on).
+(for example, Go 1.9.1, Go 1.9.2, and so on).
+</p>
+
+<h2 id="go1.9">go1.9 (released 2017/08/24)</h2>
+
+<p>
+Go 1.9 is a major release of Go.
+Read the <a href="/doc/go1.9">Go 1.9 Release Notes</a> for more information.
 </p>
 
 <h2 id="go1.8">go1.8 (released 2017/02/16)</h2>

doc/go1.9.html

@@ -15,12 +15,7 @@
 ul li { margin: 0.5em 0; }
 </style>
 
-<h2 id="introduction">DRAFT RELEASE NOTES - Introduction to Go 1.9</h2>
-
-<p><strong>
-    Go 1.9 is not yet released. These are work-in-progress
-    release notes. Go 1.9 is expected to be released in August 2017.
-</strong></p>
+<h2 id="introduction">Introduction to Go 1.9</h2>
 
 <p>
   The latest Go release, version 1.9, arrives six months
@@ -163,7 +158,7 @@ <h3 id="goroot">Moved GOROOT</h3>
   was invoked to attempt to locate the root of the Go install tree.
   This means that if the entire Go installation is moved to a new
   location, the go tool should continue to work as usual.
-  This may be overriden by setting <code>GOROOT</code> in the environment,
+  This may be overridden by setting <code>GOROOT</code> in the environment,
   which should only be done in unusual circumstances.
   Note that this does not affect the result of
   the <a href="/pkg/runtime/#GOROOT">runtime.GOROOT</a> function, which
@@ -490,7 +485,7 @@ <h3 id="minor_library_changes">Minor changes to the library</h3>
 
     <p><!-- CL 36696 -->
 
-    If any SAN extension, including with no DSN names, is present
+    If any SAN extension, including with no DNS names, is present
     in the certificate, then the Common Name from
     <a href="/pkg/crypto/x509/#Certificate.Subject"><code>Subject</code></a> is ignored.
     In previous releases, the code tested only whether DNS-name SANs were

doc/install-source.html

@@ -221,7 +221,7 @@ <h2 id="fetch">Fetch the repository</h2>
 Change to the directory that will be its parent
 and make sure the <code>go</code> directory does not exist.
 Then clone the repository and check out the latest release tag
-(<code class="versionTag">go1.8.1</code>, for example):</p>
+(<code class="versionTag">go1.9</code>, for example):</p>
 
 <pre>
 $ git clone https://go.googlesource.com/go
@@ -409,7 +409,7 @@ <h2 id="releases">Keeping up with releases</h2>
 <a href="//groups.google.com/group/golang-announce">golang-announce</a>
 mailing list.
 Each announcement mentions the latest release tag, for instance,
-<code class="versionTag">go1.8.1</code>.
+<code class="versionTag">go1.9</code>.
 </p>
 
 <p>

src/cmd/compile/internal/gc/go.go

@@ -293,4 +293,8 @@ var (
 	typedmemmove,
 	typedmemclr,
 	Udiv *obj.LSym
+
+	// GO386=387
+	ControlWord64trunc,
+	ControlWord32 *obj.LSym
 )

src/cmd/compile/internal/gc/ssa.go

@@ -92,6 +92,10 @@ func initssaconfig() {
 	typedmemmove = Sysfunc("typedmemmove")
 	typedmemclr = Sysfunc("typedmemclr")
 	Udiv = Sysfunc("udiv")
+
+	// GO386=387 runtime functions
+	ControlWord64trunc = Sysfunc("controlWord64trunc")
+	ControlWord32 = Sysfunc("controlWord32")
 }
 
 // buildssa builds an SSA function for fn.