go, branch go1.9.7

[release-branch.go1.9] go1.9.7

2018-06-06T20:29:29Z

Change-Id: I417f9b711f92d0297d9d24272cb88365cdd945d3 Reviewed-on: https://go-review.googlesource.com/116497 Run-TryBot: Filippo Valsorda Reviewed-by: Filippo Valsorda TryBot-Result: Gobot Gobot

[release-branch.go1.9] doc: document Go 1.9.7

2018-06-06T00:57:34Z

Change-Id: I10dededb41162a99dbc42792a9d314c6dabddcca Reviewed-on: https://go-review.googlesource.com/116362 Reviewed-by: Brad Fitzpatrick Reviewed-by: Russ Cox (cherry picked from commit b3a9948126471ac285e30c7920465c4c28ea0526) Reviewed-on: https://go-review.googlesource.com/116475 Reviewed-by: Filippo Valsorda

[release-branch.go1.9] cmd/go: fix 'go get' compatibility for direct download of vgo-aware module

2018-06-04T16:21:11Z

CL 109340 added “minimal module-awareness for legacy operation.” One part of that is reinterpreting imports inside code trees with go.mod files as using semantic import versioning, and converting them back to legacy import paths by stripping the major version element (for example, interpreting import "x.com/foo/v2/bar" as import "x.com/foo/bar"). This rewrite was not being applied during "go get", with the effect that once you had the target code downloaded already, everything was fine, but it didn't download and build successfully the first time. Fixes #25687. Cherry-pick fixes #25691. Change-Id: I3e122efdc8fd9a0a4e66f5aa3e6a99f90c7df779 Reviewed-on: https://go-review.googlesource.com/115797 Run-TryBot: Russ Cox TryBot-Result: Gobot Gobot Reviewed-by: Bryan C. Mills Reviewed-on: https://go-review.googlesource.com/116175

[release-branch.go1.9] cmd/go: add minimal module-awareness for legacy operation

2018-06-04T14:58:00Z

We want authors to be able to publish code that works with both the current standard go command and the planned new go command support for modules. If authors have tagged their code v2 or later, semantic import versioning means the import paths must include a v2 path element after the path prefix naming the module. One option for making this convention compatible with original go get is to move code into a v2 subdirectory of the root. That makes sense for some authors, but many authors would prefer not to move all the code into a v2 subdirectory for a transition and then move it back up once we everyone has a module-aware go command. Instead, this CL teaches the old (non-module-aware) go command a tiny amount about modules and their import paths, to expand the options for authors who want to publish compatible packages. If an author has a v2 of a package, say my/thing/v2/sub/pkg, in the my/thing repo's sub/pkg subdirectory (no v2 in the file system path), then old go get continues to import that package as my/thing/sub/pkg. But when go get is processing code in any module (code in a tree with a go.mod file) and encounters a path like my/thing/v2/sub/pkg, it will check to see if my/thing/go.mod says "module my/thing/v2". If so, the go command will read the import my/thing/v2/sub/pkg as if it said my/thing/sub/pkg, which is the correct "old" import path for the package in question. This CL will be back-ported to Go 1.10 and Go 1.9 as well. Once users have updated to the latest Go point releases containing this new logic, authors will be able to update to using modules within their own repos, including using semantic import paths with vN path elements, and old go get will still be able to consume those repositories. This CL also makes "go get" ignore meta go-import lines using the new "mod" VCS type. This allows a package to specify both a "mod" type and a "git" type, to present more efficient module access to module-aware go but still present a Git repo to the old "go get". Fixes #24751. Fixes #25069. This backport to Go 1.9 also had to pick up p.Internal.RawImports from CL 74750 and CL 74356 and use it to prepare an updated set of -importmap arguments for the compiler. (The old code only understood vendor-related rewriting of import paths.) Backport fixes #25140. Change-Id: I378955613a0d63834d4f50f121f4db7e4d87dc0a Reviewed-on: https://go-review.googlesource.com/115298 Run-TryBot: Russ Cox Reviewed-by: Bryan C. Mills Reviewed-by: Andrew Bonventre

[release-branch.go1.9] cmd/go: accept more safe CFLAGS/LDFLAGS

2018-05-31T20:11:12Z

Fixes #23749 Fixes #24703 Fixes #24858 Change-Id: Ib32d8efee294004c70fdd602087df2da0867f099 Reviewed-on: https://go-review.googlesource.com/115415 Run-TryBot: Ian Lance Taylor TryBot-Result: Gobot Gobot Reviewed-by: Brad Fitzpatrick (cherry picked from commit cc6e568c818053ddc16b80b0406a87d19de7a120) Reviewed-on: https://go-review.googlesource.com/115436 Reviewed-by: Andrew Bonventre

[release-branch.go1.9] strings: fix encoding of \u0080 in map

2018-05-26T22:48:56Z

Fix encoding of PAD (U+0080) which has the same value as utf8.RuneSelf being incorrectly encoded as \x80 in strings.Map due to using <= instead of a < comparison operator to check one byte encodings for utf8. Fixes golang/go#25573 Change-Id: Ib6c7d1f425a7ba81e431b6d64009e713d94ea3bc Reviewed-on: https://go-review.googlesource.com/111286 Run-TryBot: Martin Möhrmann TryBot-Result: Gobot Gobot Reviewed-by: Brad Fitzpatrick (cherry picked from commit 8c62fc0ca3c96ecbd3a6e81546aa8c53e32ff500) Reviewed-on: https://go-review.googlesource.com/114636 Run-TryBot: Andrew Bonventre Reviewed-by: Andrew Bonventre

[release-branch.go1.9] crypto/x509: copy and use adjusted syscall.CertChainPolicyPara

2018-05-09T14:46:40Z

As discussed in issue #21376, it is unsafe to have syscall.CertChainPolicyPara.ExtraPolicyPara uintptr - it has to be a pointer type. So copy syscall.CertChainPolicyPara into crypto/tls package, make ExtraPolicyPara unsafe.Pointer, and use new struct instead of syscall.CertChainPolicyPara. Fixes #25034 Change-Id: If914af056cbbb0c4d93ffaa915b3d2cb5ecad0cd Reviewed-on: https://go-review.googlesource.com/111715 Reviewed-by: Austin Clements Run-TryBot: Austin Clements Reviewed-on: https://go-review.googlesource.com/112179 Reviewed-by: Filippo Valsorda Run-TryBot: Filippo Valsorda TryBot-Result: Gobot Gobot

[release-branch.go1.9] misc/cgo/testcshared: use file descriptor 30 for TestUnexportedSymbols

2018-05-08T16:30:47Z

Backport of CL 108537 to 1.9 release branch. We were using file descriptor 100, which requires the Linux kernel to grow the fdtable size. That step may sometimes require a long time, causing the test to fail. Switch to file descriptor 30, which should not require growing the fdtable. Updates #23784 Fixes #25278 Change-Id: I19ea6ab1724ec1807643d5111c44631e20be76b0 Reviewed-on: https://go-review.googlesource.com/111996 Run-TryBot: Ian Lance Taylor TryBot-Result: Gobot Gobot Reviewed-by: Brad Fitzpatrick

[release-branch.go1.9] go1.9.6

2018-04-30T19:04:08Z

Change-Id: I00cd8ac03baa5961eb2b6206a4f407b5d89bcece Reviewed-on: https://go-review.googlesource.com/110336 Run-TryBot: Andrew Bonventre Reviewed-by: Andrew Bonventre TryBot-Result: Gobot Gobot

[release-branch.go1.9] doc: document Go 1.9.6

2018-04-30T18:02:05Z

Change-Id: I9699b22d3a308cda685aa684b32dcde99333df46 Reviewed-on: https://go-review.googlesource.com/110315 Reviewed-by: Filippo Valsorda (cherry picked from commit 40685b230a012dd5a9ca471dbf21b65457c32147) Reviewed-on: https://go-review.googlesource.com/110375 Reviewed-by: Andrew Bonventre