-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/go: TestScript/build_overlay broken when gccgo
is present as of CL 421879
#54761
Comments
Change https://go.dev/cl/426496 mentions this issue: |
cgo builds with -compiler=gccgo are broken as of CL 421879. For #54761. Updates #46731. Change-Id: I0306b0bd96669f70279fc96814cc72d934a1ad6e Reviewed-on: https://go-review.googlesource.com/c/go/+/426496 TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Matthew Dempsky <mdempsky@google.com> Run-TryBot: Bryan Mills <bcmills@google.com>
Change https://go.dev/cl/426155 mentions this issue: |
For the record, while I haven't looked at this specific issue yet, the general goal is for cmd/go to test what gccgo features are supported, and use those. |
That makes sense. Perhaps at some point after https://go.dev/cl/420054 lands we should add a script condition for |
Change https://go.dev/cl/446260 mentions this issue: |
…lete Test whether gccgo/GoLLVM supports cgo.Incomplete. If it doesn't, use a local definition rather than importing it. Roll back 426496, which skipped a gccgo test, as it now works. For golang#46731 Fixes golang#54761 Change-Id: I8bb2ad84c317094495405e178bf5c9694f82af56 Reviewed-on: https://go-review.googlesource.com/c/go/+/446260 Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
https://go.dev/cl/421879 caused
go build --compiler=gccgo
to fail when the installedgccgo
predates theruntime/cgo
changes in that CL.I'm not sure what exactly, if anything, we should do about that, since we can't in general make assumptions about which
gccgo
the user may have installed.@ianlancetaylor, @cuonglm: any suggestions? (For now I'm going to disable that part of the test.)
The text was updated successfully, but these errors were encountered: