Commit be9f10b2 authored by Brad Fitzpatrick's avatar Brad Fitzpatrick

cmd/go/internal/work: fix a couple typos

Change-Id: I357669d8c9bc004031b17f057803c9b152edefee
Reviewed-on: https://go-review.googlesource.com/c/go/+/178057Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
parent 5eeb3724
...@@ -159,7 +159,7 @@ func hashToString(h [cache.HashSize]byte) string { ...@@ -159,7 +159,7 @@ func hashToString(h [cache.HashSize]byte) string {
// which influences the action ID half of the build ID, is based on the content ID, // which influences the action ID half of the build ID, is based on the content ID,
// then the Linux compiler binary and Mac compiler binary will have different tool IDs // then the Linux compiler binary and Mac compiler binary will have different tool IDs
// and therefore produce executables with different action IDs. // and therefore produce executables with different action IDs.
// To avoids this problem, for releases we use the release version string instead // To avoid this problem, for releases we use the release version string instead
// of the compiler binary's content hash. This assumes that all compilers built // of the compiler binary's content hash. This assumes that all compilers built
// on all different systems are semantically equivalent, which is of course only true // on all different systems are semantically equivalent, which is of course only true
// modulo bugs. (Producing the exact same executables also requires that the different // modulo bugs. (Producing the exact same executables also requires that the different
...@@ -215,7 +215,7 @@ func (b *Builder) toolID(name string) string { ...@@ -215,7 +215,7 @@ func (b *Builder) toolID(name string) string {
} }
// gccToolID returns the unique ID to use for a tool that is invoked // gccToolID returns the unique ID to use for a tool that is invoked
// by the GCC driver. This is in particular gccgo, but this can also // by the GCC driver. This is used particularly for gccgo, but this can also
// be used for gcc, g++, gfortran, etc.; those tools all use the GCC // be used for gcc, g++, gfortran, etc.; those tools all use the GCC
// driver under different names. The approach used here should also // driver under different names. The approach used here should also
// work for sufficiently new versions of clang. Unlike toolID, the // work for sufficiently new versions of clang. Unlike toolID, the
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment