From: Russ Cox Date: Tue, 9 Jan 2018 20:26:21 +0000 (-0500) Subject: doc: s/tool chain/toolchain/ X-Git-Tag: go1.10beta2~28 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=b6c871a2af7c916f3c862e38816713aa8bf824a0;p=gostls13.git doc: s/tool chain/toolchain/ We were not being consistent. Standardize on toolchain. Change-Id: Id0e756b5214ce4a1341f733634ed95263f03a61c Reviewed-on: https://go-review.googlesource.com/87017 Run-TryBot: Russ Cox Reviewed-by: Brad Fitzpatrick Reviewed-by: Ian Lance Taylor --- diff --git a/doc/articles/go_command.html b/doc/articles/go_command.html index 0fd83cb53a..9f4e8e0631 100644 --- a/doc/articles/go_command.html +++ b/doc/articles/go_command.html @@ -134,7 +134,7 @@ be able to adapt to changing build environments and conditions. For example, if we allowed extra configuration such as compiler flags or command line recipes, then that configuration would need to be updated each time the build tools changed; it would also be inherently tied -to the use of a specific tool chain.

+to the use of a specific toolchain.

Getting started with the go command

diff --git a/doc/asm.html b/doc/asm.html index e3e17f85f5..3a05d46aeb 100644 --- a/doc/asm.html +++ b/doc/asm.html @@ -29,7 +29,7 @@ Instead, the compiler operates on a kind of semi-abstract instruction set, and instruction selection occurs partly after code generation. The assembler works on the semi-abstract form, so when you see an instruction like MOV -what the tool chain actually generates for that operation might +what the toolchain actually generates for that operation might not be a move instruction at all, perhaps a clear or load. Or it might correspond exactly to the machine instruction with that name. In general, machine-specific operations tend to appear as themselves, while more general concepts like @@ -139,7 +139,7 @@ The exact set depends on the architecture.

There are four predeclared symbols that refer to pseudo-registers. These are not real registers, but rather virtual registers maintained by -the tool chain, such as a frame pointer. +the toolchain, such as a frame pointer. The set of pseudo-registers is the same for all architectures:

diff --git a/doc/debugging_with_gdb.html b/doc/debugging_with_gdb.html index f3333fe894..ed59cc8a57 100644 --- a/doc/debugging_with_gdb.html +++ b/doc/debugging_with_gdb.html @@ -13,7 +13,7 @@ Gccgo has native gdb support. Note that Delve is a better alternative to GDB when debugging Go programs built with the standard -tool chain. It understands the Go runtime, data structures, and +toolchain. It understands the Go runtime, data structures, and expressions better than GDB. Delve currently supports Linux, OSX, and Windows on amd64. For the most up-to-date list of supported platforms, please see @@ -113,7 +113,7 @@ Show the name, type and location of global variables:

A recent extension mechanism to GDB allows it to load extension scripts for a -given binary. The tool chain uses this to extend GDB with a handful of +given binary. The toolchain uses this to extend GDB with a handful of commands to inspect internals of the runtime code (such as goroutines) and to pretty print the built-in map, slice and channel types.

diff --git a/doc/go1.1.html b/doc/go1.1.html index f059fd7f1f..f615c97e81 100644 --- a/doc/go1.1.html +++ b/doc/go1.1.html @@ -166,7 +166,7 @@ providing a complete Go 1.1 implementation.

Command-line flag parsing

-In the gc tool chain, the compilers and linkers now use the +In the gc toolchain, the compilers and linkers now use the same command-line flag parsing rules as the Go flag package, a departure from the traditional Unix flag parsing. This may affect scripts that invoke the tool directly. @@ -305,7 +305,7 @@ The race detector is documented in a

Due to the change of the int to 64 bits and a new internal representation of functions, -the arrangement of function arguments on the stack has changed in the gc tool chain. +the arrangement of function arguments on the stack has changed in the gc toolchain. Functions written in assembly will need to be revised at least to adjust frame pointer offsets.

@@ -395,7 +395,7 @@ Run go help test for more information. The fix command, usually run as go fix, no longer applies fixes to update code from before Go 1 to use Go 1 APIs. -To update pre-Go 1 code to Go 1.1, use a Go 1.0 tool chain +To update pre-Go 1 code to Go 1.1, use a Go 1.0 toolchain to convert the code to Go 1.0 first.

@@ -427,7 +427,7 @@ To build a file only with Go 1.0.x, use the converse constraint:

Additional platforms

-The Go 1.1 tool chain adds experimental support for freebsd/arm, +The Go 1.1 toolchain adds experimental support for freebsd/arm, netbsd/386, netbsd/amd64, netbsd/arm, openbsd/386 and openbsd/amd64 platforms.

diff --git a/doc/go1.2.html b/doc/go1.2.html index b9d36f29c3..5370bbbbd6 100644 --- a/doc/go1.2.html +++ b/doc/go1.2.html @@ -266,7 +266,7 @@ is now an error.

On the ARM, the toolchain supports "external linking", which is a step towards being able to build shared libraries with the gc -tool chain and to provide dynamic linking support for environments +toolchain and to provide dynamic linking support for environments in which that is necessary.

diff --git a/doc/go1.3.html b/doc/go1.3.html index d51052b2e5..18c638a1b5 100644 --- a/doc/go1.3.html +++ b/doc/go1.3.html @@ -11,7 +11,7 @@ The latest Go release, version 1.3, arrives six months after 1.2, and contains no language changes. It focuses primarily on implementation work, providing precise garbage collection, -a major refactoring of the compiler tool chain that results in +a major refactoring of the compiler toolchain that results in faster builds, especially for large projects, significant performance improvements across the board, and support for DragonFly BSD, Solaris, Plan 9 and Google's Native Client architecture (NaCl). @@ -285,7 +285,7 @@ building and linking with a shared library.

Command-line flag parsing

-In the gc tool chain, the assemblers now use the +In the gc toolchain, the assemblers now use the same command-line flag parsing rules as the Go flag package, a departure from the traditional Unix flag parsing. This may affect scripts that invoke the tool directly. diff --git a/doc/go1compat.html b/doc/go1compat.html index 607d354687..a5624ef5f6 100644 --- a/doc/go1compat.html +++ b/doc/go1compat.html @@ -190,8 +190,8 @@ For details and background, see

Tools

-Finally, the Go tool chain (compilers, linkers, build tools, and so -on) are under active development and may change behavior. This +Finally, the Go toolchain (compilers, linkers, build tools, and so +on) is under active development and may change behavior. This means, for instance, that scripts that depend on the location and properties of the tools may be broken by a point release.

diff --git a/doc/go_faq.html b/doc/go_faq.html index a3cb8731fa..c038bc46bd 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -1842,7 +1842,7 @@ supported by recent modifications to the gold linker. Why is my trivial program such a large binary?

-The linker in the gc tool chain +The linker in the gc toolchain creates statically-linked binaries by default. All Go binaries therefore include the Go run-time, along with the run-time type information necessary to support dynamic type checks, reflection, and even panic-time stack traces. diff --git a/doc/install-source.html b/doc/install-source.html index 17b6ed3ea1..8813455cbc 100644 --- a/doc/install-source.html +++ b/doc/install-source.html @@ -24,7 +24,7 @@ packages, though, read on.

-There are two official Go compiler tool chains. +There are two official Go compiler toolchains. This document focuses on the gc Go compiler and tools. For information on how to work on gccgo, a more traditional @@ -119,7 +119,7 @@ Go does not support CentOS 6 on these systems.

Install Go compiler binaries

-The Go tool chain is written in Go. To build it, you need a Go compiler installed. +The Go toolchain is written in Go. To build it, you need a Go compiler installed. The scripts that do the initial build of the tools look for an existing Go tool chain in $GOROOT_BOOTSTRAP. If unset, the default value of GOROOT_BOOTSTRAP @@ -127,26 +127,26 @@ is $HOME/go1.4.

-There are many options for the bootstrap tool chain. +There are many options for the bootstrap toolchain. After obtaining one, set GOROOT_BOOTSTRAP to the directory containing the unpacked tree. For example, $GOROOT_BOOTSTRAP/bin/go should be -the go command binary for the bootstrap tool chain. +the go command binary for the bootstrap toolchain.

-To use a binary release as a bootstrap tool chain, see +To use a binary release as a bootstrap toolchain, see the downloads page or use any other packaged Go distribution.

-To build a bootstrap tool chain from source, use +To build a bootstrap toolchain from source, use either the git branch release-branch.go1.4 or go1.4-bootstrap-20171003.tar.gz, which contains the Go 1.4 source code plus accumulated fixes to keep the tools running on newer operating systems. -(Go 1.4 was the last distribution in which the tool chain was written in C.) +(Go 1.4 was the last distribution in which the toolchain was written in C.) After unpacking the Go 1.4 source, cd to the src subdirectory, set CGO_ENABLED=0 in the environment, and run make.bash (or, @@ -154,7 +154,7 @@ on Windows, make.bat).

-To cross-compile a bootstrap tool chain from source, which is +To cross-compile a bootstrap toolchain from source, which is necessary on systems Go 1.4 did not target (for example, linux/ppc64le), install Go on a different system and run bootstrap.bash.