-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: internal compiler error: assertion failed [1.18 backport] #53852
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
460a93b seems to be the culprit, reverting it fixes the build. |
It's weird that checkout 7eeec1f on master branch works. |
So I think the problem is that with the master, we use method expression closures to implement bound method calls, which is implemented in 2 CLs: So the bound method calls in:
is not cast anymore. I'm not sure what should we do in this case, cherry pick those 2 CLs? cc @randall77 @mdempsky |
I think let's revert the backport CL. Go 1.19 will be out soon, and I think it's more important in the mean time that we don't destabilize the Go 1.18 release branch. |
Change https://go.dev/cl/417615 mentions this issue: |
@mknyszek @mdempsky This issue is currently in Backlog milestone, which probably needs updating. Do you think it's better to move this issue to Go1.19 milestone and close it (since it's fixed at tip) and ask gopherbot to file a backport issue for 1.18 which will create an issue in the right milestone—or would it work better to just manually edit this issue to be a Go 1.18 backport issue? |
@dmitshur The issue here is exclusive to the Go 1.18 release branch, as far as I can tell, so I've assigned to 1.18.5. We discussed this internally amongst the Google Go compiler and runtime team, and consensus is to simply revert any problematic backported CLs and stop backporting further generics CLs to 1.18. It's unfortunate that 1.18.* will continue having generics correctness issues, but we think it's better those issues remain stable across point releases so users can reliably upgrade to get security fixes. |
Revert https://go-review.googlesource.com/c/go/+/411617 that introduced the regression that broke security/gopass and security/git-credential-gopass. See golang/go#53852 for more details.
Revert https://go-review.googlesource.com/c/go/+/411617 that introduced the regression that broke security/gopass and security/git-credential-gopass. See golang/go#53852 for more details. Approved by: portmgr blanket (build fix) (cherry picked from commit e57c55d)
This is also an issue on go version go1.18.4 linux/amd64. You can use the same repo mentioned for FreeBSD to get the error on Linux. |
Closed by merging 6ff8801 to release-branch.go1.18. |
…r type assertions" This reverts CL 411934 (commit 460a93b). Fixes #53852. Updates #53357. Change-Id: I93d7015d8962d22ffd73128b038e4e7e7ca41c2f Reviewed-on: https://go-review.googlesource.com/c/go/+/417615 Run-TryBot: Cherry Mui <[email protected]> Reviewed-by: Cuong Manh Le <[email protected]> Reviewed-by: David Chase <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
This seems to be a regression in go1.18.4.
Both go1.18.3 and the current tip (go version devel go1.19-c006b7ac27 Wed Jul 13 18:35:00 2022 +0000 freebsd/amd64) do not have this issue.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
A successful build.
What did you see instead?
See also #53762
cc @golang/compiler
The text was updated successfully, but these errors were encountered: