aboutsummaryrefslogtreecommitdiff
path: root/doc/asm.html
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2018-01-09 15:26:21 -0500
committerRuss Cox <rsc@golang.org>2018-01-09 21:47:03 +0000
commitb6c871a2af7c916f3c862e38816713aa8bf824a0 (patch)
tree8ed9612371d4bd8aa4627313c95662bf12c98c4e /doc/asm.html
parentdd806b8be4447f064e93ad9302bc8befde37f952 (diff)
downloadgo-b6c871a2af7c916f3c862e38816713aa8bf824a0.tar.gz
go-b6c871a2af7c916f3c862e38816713aa8bf824a0.zip
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 <rsc@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
Diffstat (limited to 'doc/asm.html')
-rw-r--r--doc/asm.html4
1 files changed, 2 insertions, 2 deletions
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 <code>MOV</code>
-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.
<p>
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:
</p>