-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: when building gccgo, GOPKGPATH encoding does not match pkgpath encoding #37272
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
What's odd is that there's gccgo code in Running
so the function definition is there. That naming is coming from an ASM label in
It appears that gccgo isn't following this naming convention? I'm not sure where this sort of thing is documented. At any rate, the problem can be fixed by commenting out the ASM labelling and switching to
|
It's a bug in the go tool. The GOPKGPATH macro is supposed to be defined to the encoding of the pkgpath. But when we changed the pkgpath encoding in https://golang.org/cl/135455 and https://golang.org/cl/200838 we didn't update the go tool accordingly. CC @thanm |
Change https://golang.org/cl/219817 mentions this issue: |
This will need to be done in the gc version too, probably more cleverly. This version will ensure that the next GCC release works correctly when using the GCC version of the go tool. Updates golang/go#37272 Change-Id: I5636bec7268bcd41994c2e2262f8293cb95c0cd4 Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/219817 Reviewed-by: Than McIntosh <[email protected]>
This will need to be done in the gc version too, probably more cleverly. This version will ensure that the next GCC release works correctly when using the GCC version of the go tool. Updates golang/go#37272 Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/219817
Moving to backlog milestone. This should still be fixed in the gc version of cmd/go. |
Change https://golang.org/cl/259298 mentions this issue: |
Change https://golang.org/cl/259299 mentions this issue: |
This is a step toward porting https://golang.org/cl/219817 from the gofrontend repo to the main repo. Note that this also corrects the implementation of the v2 mangling scheme to use ..u and ..U where appropriate. For #37272 Change-Id: I64a1e7ca1c84348efcbf1cf62049eeb05c830ed8 Reviewed-on: https://go-review.googlesource.com/c/go/+/259298 Trust: Ian Lance Taylor <[email protected]> Run-TryBot: Ian Lance Taylor <[email protected]> TryBot-Result: Go Bot <[email protected]> Reviewed-by: Than McIntosh <[email protected]>
Change https://golang.org/cl/270637 mentions this issue: |
This is a port of two patches in the master repository. https://golang.org/cl/259298 cmd/cgo: split gofrontend mangling checks into cmd/internal/pkgpath This is a step toward porting https://golang.org/cl/219817 from the gofrontend repo to the main repo. Note that this also corrects the implementation of the v2 mangling scheme to use ..u and ..U where appropriate. https://golang.org/cl/259299 cmd/go: use cmd/internal/pkgpath for gccgo pkgpath symbol For golang/go#37272 For golang/go#41862 Change-Id: Id276ca1bac7e1d850408a9d222c19e57b26ba001 Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/270637 Trust: Ian Lance Taylor <[email protected]> Reviewed-by: Than McIntosh <[email protected]>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I'm using
gccgo-9
, which I think is the latest release.What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Code: https://play.golang.org/p/CwSEukNuiAg
Building with regular go works:
while building with gccgo fails:
What did you expect to see?
Build success.
What did you see instead?
Build failure.
The text was updated successfully, but these errors were encountered: