-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/link: request backport for ppc64le linker fix to go 1.8 #20670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'll let @ianlancetaylor decide. But we may be closed enough to Go 1.9 that the answer might be to wait. |
I think it's OK to backport the CL for 1.8, but it's not enough to trigger a 1.8.4 release. We may never do a 1.8.4 release. I would suggest preparing the CL at your leisure, but don't commit it to the branch. |
CL https://golang.org/cl/45756 mentions this issue. |
@jcajka The above CL is the Go 1.8 backport of the fix for openshift on ppc64le. |
|
go1.8.5 has been packaged and includes: The release is posted at golang.org/dl. — golang.org/x/build/cmd/releasebot, Oct 26 21:07:49 UTC |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go 1.8.3
What operating system and processor architecture are you using (
go env
)?Ubuntu ppc64le
A fix went upstream related to linking programs on ppc64le, affecting the build of very large programs as are found in Kubernetes and openshift. I'm requesting to backport this fix to the go 1.8 branch so it is in a go1.8.x, since many builds are still using go 1.8.x and will continue to use that version for a while.
The issue is #20497 fixed by CL 45130. If this is approved, I can take care of doing the backport.
The text was updated successfully, but these errors were encountered: