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/dist: GOARM inference fails with arm64 kernel #12548
Comments
Sounds fine. |
Could we reconsider restoring the automatic detection feature?
CL 3973.
|
The build is slow enough. I don't want to see it compiling and running a program for a simple check. Can you modify CL 3973 to make it compile those two probe functions into the dist binary itself, and then just make dist exec its own binary (argv[0]) as a child to do the probe and see whether it crashes? It would at least eliminate the extra compile and disk I/O. |
CL https://golang.org/cl/14413 mentions this issue. |
I will update CL 3973 to do the re-exec itself trick.
I didn't do it before because I was concerned that
os.Args[0] might not be pointing to the program,
and we don't have a portable way to get the current
process' executable path.
|
CL https://golang.org/cl/3973 mentions this issue. |
cmd/dist will re-exec itself to detect VFP support at run-time. Fixes #9732, #12548. Change-Id: I9ad0c5c7fa3e97bd79a32da372e1a962565bb3af Reviewed-on: https://go-review.googlesource.com/3973 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Minux's CL fixed this. |
Fixes golang#12548 Change-Id: I6727a49d7da1167a5f72608399c98b33b9a5d1df
This is a selfish bug report: the fastest and most reliable 32-bit arm environment I have access to is a armhf chroot on an arm64 system and currently I'm fairly sure it falls back to GOARM=5 when running ./all.bash. I think checking assuming GOARM=7 when uname -m == armv8l would be appropriate.
The text was updated successfully, but these errors were encountered: