-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/compile: go test . results in CLOSURE ... <unknown line number>: internal compiler error: assertion failed #65593
Comments
Simpler reproducer:
|
Stack trace, at tip, from the @cuonglm reproducer. Looking at who-touched-it-last and the code involved, might be related to code for the rangefunc experiment.
|
@dr2chase I think the assertion is there before rangefunc added. The rangefunc code just add the dumping of closurevars. This seems to be the issue with deadcode pass, which was moved to unified IR writer in https://go-review.googlesource.com/c/go/+/517775 cc @mdempsky |
We appear to be running into this with the GitHub CLI being built for windows on go 1.22. It doesn't seem to reproduce with |
Change https://go.dev/cl/565596 mentions this issue: |
@gopherbot Please open a backport issue for 1.22. |
Backport issue(s) opened: #66134 (for 1.22). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Go version
go1.22.0 linux/amd64
Output of
go env
in your module/workspace:What did you do?
Test upgrading some things to go 1.22.0, was able to cut it down to fairly small reproducer (Which also fails on the playground, yay!):
https://go.dev/play/p/SrzHxxnTmm7
What did you see happen?
CLOSURE [prog_test.go:14:12:var messages chan struct{}]
: internal compiler error: assertion failed
Please file a bug report including a short program that triggers the error.
https://go.dev/issue/new
What did you expect to see?
Anything other than an assertion failed
The text was updated successfully, but these errors were encountered: