-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/compile: bootstrap crashes out with illegal instruction on ppc64 #24358
Comments
Starting with go 1.9, the minimum supported instruction set is power8 for both ppc64 and ppc64le. If you are on power7 or earlier you will get a SIGILL on the lbarx because that is new in power8. This is documented in https://golang.org/doc/go1.9. |
Yes, I became aware of this and the associated issue. It seems quite silly on the ppc64 big-endian side, because there's essentially no reason to run big-endian on POWER8. |
@NattyNarwhal what is your suggested course of action? |
I had to roll back to 1.8.7 so it could run on the POWER6 system. It seems silly to me to make ppc64 require POWER8 when everyone on a POWER8 is almost certainly running ppc64le; so I'd be one of the people recommending that ppc64 support older processors. |
Thanks for the clarification. In that case, I would continue the conversation on #19074 and/or write a proposal (golang.org/s/proposal) making a case to support older processors for ppc64. The issue you are describing is working as intended (at the moment). Your suggested change to support older processors falls outside the scope of this (more specific) report. Hope this helps. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.6 linux/amd64 (to start bootstrapping with)
trying to build 1.10
Does this issue reproduce with the latest release?
Trying to build latest stable: 1.10.
What operating system and processor architecture are you using (
go env
)?On local system:
Remote system: trying to build for Linux/ppc64
What did you do?
Copied the created tarball over, then ran the go binary contained within to see if it worked.
What did you expect to see?
The cross-compile starting
What did you see instead?
The text was updated successfully, but these errors were encountered: