Wasm WIP

.github/SUPPORT.md

@@ -9,6 +9,6 @@ For asking questions, see:
 
 * [Gophers Slack](https://gophers.slack.com), use the [invite app](https://invite.slack.golangbridge.org/) for access
 
-* [Stack Overflow](http://stackoverflow.com/questions/tagged/go) with questions tagged "go"
+* [Stack Overflow](https://stackoverflow.com/questions/tagged/go) with questions tagged "go"
 
 * **IRC** channel #go-nuts on Freenode

Dockerfile

@@ -0,0 +1,20 @@
+FROM golang:1.10-alpine
+
+RUN apk add --no-cache bash build-base nodejs
+
+ENV GOROOT=/usr/local/go-wasm
+ADD src $GOROOT/src
+ADD misc $GOROOT/misc
+ADD test $GOROOT/test
+RUN ln -s $GOROOT/misc/wasm/go_js_wasm_exec /usr/local/bin/go_js_wasm_exec
+
+RUN echo "dev" > $GOROOT/VERSION
+RUN cd $GOROOT/src && ./make.bash
+ENV PATH=$GOROOT/bin:$PATH
+RUN cd $GOROOT/test && go build run.go
+
+ENV GOARCH=wasm
+ENV GOOS=js
+RUN go install -v std
+RUN go test -short std
+RUN cd $GOROOT/test && ./run -v

README.md

@@ -19,14 +19,14 @@ BSD-style license found in the LICENSE file.
 Official binary distributions are available at https://golang.org/dl/.
 
 After downloading a binary release, visit https://golang.org/doc/install
-or load doc/install.html in your web browser for installation
+or load [doc/install.html](./doc/install.html) in your web browser for installation
 instructions.
 
 #### Install From Source
 
 If a binary distribution is not available for your combination of
 operating system and architecture, visit
-https://golang.org/doc/install/source or load doc/install-source.html
+https://golang.org/doc/install/source or load [doc/install-source.html](./doc/install-source.html)
 in your web browser for source installation instructions.
 
 ### Contributing

api/except.txt

@@ -377,9 +377,11 @@ pkg syscall (windows-386), type CertContext struct, CertInfo uintptr
 pkg syscall (windows-386), type CertRevocationInfo struct, CrlInfo uintptr
 pkg syscall (windows-386), type CertRevocationInfo struct, OidSpecificInfo uintptr
 pkg syscall (windows-386), type CertSimpleChain struct, TrustListInfo uintptr
+pkg syscall (windows-386), const TOKEN_ALL_ACCESS = 983295
 pkg syscall (windows-amd64), type CertChainPolicyPara struct, ExtraPolicyPara uintptr
 pkg syscall (windows-amd64), type CertChainPolicyStatus struct, ExtraPolicyStatus uintptr
 pkg syscall (windows-amd64), type CertContext struct, CertInfo uintptr
 pkg syscall (windows-amd64), type CertRevocationInfo struct, CrlInfo uintptr
 pkg syscall (windows-amd64), type CertRevocationInfo struct, OidSpecificInfo uintptr
 pkg syscall (windows-amd64), type CertSimpleChain struct, TrustListInfo uintptr
+pkg syscall (windows-amd64), const TOKEN_ALL_ACCESS = 983295

doc/code.html

@@ -110,6 +110,10 @@ <h3 id="Workspaces">Workspaces</h3>
 and dependencies in a single workspace.
 </p>
 
+<p>
+Note that symbolic links should <b>not</b> be used to link files or directories into your workspace.
+</p>
+
 <p>
 Commands and libraries are built from different kinds of source packages.
 We will discuss the distinction <a href="#PackageNames">later</a>.
@@ -669,7 +673,7 @@ <h2 id="help">Getting help</h2>
 
 <p>
 For real-time help, ask the helpful gophers in <code>#go-nuts</code> on the
-<a href="http://freenode.net/">Freenode</a> IRC server.
+<a href="https://freenode.net/">Freenode</a> IRC server.
 </p>
 
 <p>

doc/contribute.html

@@ -418,7 +418,7 @@ <h3>Overview</h3>
 
 <li>
 <b>Step 4:</b> Send the changes for review to Gerrit using <code>git</code>
-<code>codereview</code> <code>mail</code>(which doesn't use e-mail, despite the name).
+<code>codereview</code> <code>mail</code> (which doesn't use e-mail, despite the name).
 <pre>
 $ git codereview mail     # send changes to Gerrit
 </pre>
@@ -639,7 +639,7 @@ <h2 id="commit_messages">Good commit messages</h2>
 large arguments, so use the McGillicutty algorithm to improve
 accuracy above 1e10.
 
-The algorithm is described at http://wikipedia.org/wiki/McGillicutty_Algorithm
+The algorithm is described at https://wikipedia.org/wiki/McGillicutty_Algorithm
 
 Fixes #159
 </pre>
@@ -984,8 +984,8 @@ <h3 id="quick_test">Quickly testing your changes</h3>
 
 <li>
 In this section, we'll call the directory into which you cloned the Go repository <code>$GODIR</code>.
-The <code>go</code> tool built by <code>$GODIR/make.bash</code>will be installed
-in <code>$GODIR/bin/go</code>and you
+The <code>go</code> tool built by <code>$GODIR/make.bash</code> will be installed
+in <code>$GODIR/bin/go</code> and you
 can invoke it to test your code.
 For instance, if you
 have modified the compiler and you want to test how it affects the

doc/debugging_with_gdb.html

@@ -47,7 +47,7 @@
 to use GDB when it works, not as a guarantee of success.
 
 Besides this overview you might want to consult the
-<a href="http://sourceware.org/gdb/current/onlinedocs/gdb/">GDB manual</a>.
+<a href="https://sourceware.org/gdb/current/onlinedocs/gdb/">GDB manual</a>.
 </p>
 
 <p>

doc/devel/release.html

@@ -48,6 +48,15 @@ <h3 id="go1.10.minor">Minor revisions</h3>
 1.10.2 milestone</a> on our issue tracker for details.
 </p>
 
+<p>
+go1.10.3 (released 2018/06/05) includes fixes to the go command, and the
+<code>crypto/tls</code>, <code>crypto/x509</code>, and <code>strings</code> packages.
+In particular, it adds <a href="https://go.googlesource.com/go/+/d4e21288e444d3ffd30d1a0737f15ea3fc3b8ad9">
+minimal support to the go command for the vgo transition</a>.
+See the <a href="https://github.com/golang/go/issues?q=milestone%3AGo1.10.3">Go
+1.10.3 milestone</a> on our issue tracker for details.
+</p>
+
 <h2 id="go1.9">go1.9 (released 2017/08/24)</h2>
 
 <p>
@@ -101,6 +110,15 @@ <h3 id="go1.9.minor">Minor revisions</h3>
 1.9.6 milestone</a> on our issue tracker for details.
 </p>
 
+<p>
+go1.9.7 (released 2018/06/05) includes fixes to the go command, and the
+<code>crypto/x509</code>, and <code>strings</code> packages.
+In particular, it adds <a href="https://go.googlesource.com/go/+/d4e21288e444d3ffd30d1a0737f15ea3fc3b8ad9">
+minimal support to the go command for the vgo transition</a>.
+See the <a href="https://github.com/golang/go/issues?q=milestone%3AGo1.9.7">Go
+1.9.7 milestone</a> on our issue tracker for details.
+</p>
+
 
 <h2 id="go1.8">go1.8 (released 2017/02/16)</h2>
 

doc/docs.html

@@ -195,7 +195,7 @@ <h2 id="talks">Talks</h2>
 
 <img class="gopher" src="/doc/gopher/talks.png"/>
 
-<h3 id="video_tour_of_go"><a href="http://research.swtch.com/gotour">A Video Tour of Go</a></h3>
+<h3 id="video_tour_of_go"><a href="https://research.swtch.com/gotour">A Video Tour of Go</a></h3>
 <p>
 Three things that make Go fast, fun, and productive:
 interfaces, reflection, and concurrency. Builds a toy web crawler to

doc/editors.html

@@ -9,7 +9,7 @@ <h2 id="introduction">Introduction</h2>
   This document lists commonly used editor plugins and IDEs from the Go ecosystem
   that make Go development more productive and seamless.
   A comprehensive list of editor support and IDEs for Go development is available at
-  <a href="http://golang.org/wiki/IDEsAndTextEditorPlugins">the wiki</a>.
+  <a href="https://golang.org/wiki/IDEsAndTextEditorPlugins">the wiki</a>.
 </p>
 
 <h2 id="options">Options</h2>

doc/gccgo_contribute.html

@@ -22,17 +22,17 @@ <h2>Legal Prerequisites</h2>
 You must follow the <a href="/doc/contribute.html#copyright">Go copyright
 rules</a> for all changes to the gccgo frontend and the associated
 libgo library.  Code that is part of GCC rather than gccgo must follow
-the general <a href="http://gcc.gnu.org/contribute.html">GCC
+the general <a href="https://gcc.gnu.org/contribute.html">GCC
 contribution rules</a>.
 </p>
 
 <h2>Code</h2>
 
 <p>
 The master sources for the gccgo frontend may be found at
-<a href="http://go.googlesource.com/gofrontend">http://go.googlesource.com/gofrontend</a>.
+<a href="https://go.googlesource.com/gofrontend">https://go.googlesource.com/gofrontend</a>.
 They are mirrored
-at <a href="http://github.com/golang/gofrontend">http://github.com/golang/gofrontend</a>.
+at <a href="https://github.com/golang/gofrontend">https://github.com/golang/gofrontend</a>.
 The master sources are not buildable by themselves, but only in
 conjunction with GCC (in the future, other compilers may be
 supported).  Changes made to the gccgo frontend are also applied to

doc/gccgo_install.html

@@ -9,7 +9,7 @@
 for GCC, the widely used GNU compiler.  Although the
 frontend itself is under a BSD-style license, gccgo is
 normally used as part of GCC and is then covered by
-the <a href="http://www.gnu.org/licenses/gpl.html">GNU General Public
+the <a href="https://www.gnu.org/licenses/gpl.html">GNU General Public
 License</a> (the license covers gccgo itself as part of GCC; it
 does not cover code generated by gccgo).
 </p>
@@ -25,7 +25,7 @@ <h2 id="Releases">Releases</h2>
 <p>
 The simplest way to install gccgo is to install a GCC binary release
 built to include Go support.  GCC binary releases are available from
-<a href="http://gcc.gnu.org/install/binaries.html">various
+<a href="https://gcc.gnu.org/install/binaries.html">various
 websites</a> and are typically included as part of GNU/Linux
 distributions.  We expect that most people who build these binaries
 will include Go support.
@@ -79,7 +79,7 @@ <h2 id="Source_code">Source code</h2>
 yourself, 
 the gccgo source code is accessible via Subversion.  The
 GCC web site
-has <a href="http://gcc.gnu.org/svn.html">instructions for getting the
+has <a href="https://gcc.gnu.org/svn.html">instructions for getting the
 GCC source code</a>.  The gccgo source code is included.  As a
 convenience, a stable version of the Go support is available in
 a branch of the main GCC code
@@ -101,7 +101,7 @@ <h2 id="Building">Building</h2>
 <p>
 Building gccgo is just like building GCC
 with one or two additional options.  See
-the <a href="http://gcc.gnu.org/install/">instructions on the gcc web
+the <a href="https://gcc.gnu.org/install/">instructions on the gcc web
 site</a>.  When you run <code>configure</code>, add the
 option <code>--enable-languages=c,c++,go</code> (along with other
 languages you may want to build).  If you are targeting a 32-bit x86,
@@ -156,7 +156,7 @@ <h3 id="Prerequisites">Prerequisites</h3>
 <p>
 A number of prerequisites are required to build GCC, as
 described on
-the <a href="http://gcc.gnu.org/install/prerequisites.html">gcc web
+the <a href="https://gcc.gnu.org/install/prerequisites.html">gcc web
 site</a>.  It is important to install all the prerequisites before
 running the gcc <code>configure</code> script.
 The prerequisite libraries can be conveniently downloaded using the