-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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/link: misc/cgo/testshared fail on ARM64 #17642
Comments
I presume this is 8b07ec2. Where has the arm64 builder gone? :( |
Although that worked when backported to 1.7 on Ubuntu zesty: https://launchpadlibrarian.net/291097700/buildlog_ubuntu-zesty-arm64.golang-1.7_1.7.3-1ubuntu2_BUILDING.txt.gz -- which version of gold do you have installed? |
I am wondering it, too. |
|
Looks like this was fixed in October 2015 (https://sourceware.org/bugzilla/show_bug.cgi?id=19042) which I think means binutils 2.26. I'm a bit confused as to how this is happening. Can you confirm that it really is the commit I mentioned that causes the problem? (I don't have easy access to an arm64 system with a sufficiently old version of gold installed). |
Thank you for investigation. Yes, it is indeed that commit. I tested it and one commit before to confirm. So, the problem seems that my gold linker is too old? Are we going to require a newer version? At the least we should document it, though I'm not sure where. |
Change-Id: I4ba060bb1ce73a527ce276e5a769c44692b50016
Well there is something strange going on in that we really shouldn't be accessing a local symbol via the GOT. Can you see if mwhudson@f30efbd helps? |
This indeed works. Thank you! (I have not tested on other architectures though.) |
CL https://golang.org/cl/32236 mentions this issue. |
What version of Go are you using (
go version
)?tip +bba1ac4
What operating system and processor architecture are you using (
go env
)?linux/arm64
It wasn't broken yesterday when I tested my CL 32180 locally. So, I think it is probably somewhere between 829aa67 and bba1ac4.
The text was updated successfully, but these errors were encountered: