-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: internal compiler error: panic during expand calls [since go1.16] #49249
Comments
Change https://golang.org/cl/360057 mentions this issue: |
@ALTree you can remove all the empty assignments, and compile with inlining disable to trigger the bug. The problem is that we haven't updated the source type after removing trivial wrapper types. Not sure it's qualified for backporting cc @randall77 @dr2chase |
Kindly ping @randall77 @dr2chase to decide whether we should backport this. |
Seems safe. @drchase, would it be needed in 1.16, or just 1.17? |
Hi, sorry for the delay. The fix that needs backporting is https://go-review.googlesource.com/c/go/+/361594. Seems like 1.17 and 1.16, if it crashes for both. |
So it's #49387 which needs to be backported. But the test there won't crash for 1.16 and 1.17, only the test in this issue does. |
The Go 1.16, 1.17, and tip compilers all crash with this error:
when compiling this program:
Go1.15 seems to work fine.
git bisect
says this started at 15f01d6.The reproducer is minimized, the many silly empty assignments are not the culprit. The same crash can be triggered with a function with more meaningful statements and expressions, as long as it has enough values in its body.
cc @dr2chase @randall77
The text was updated successfully, but these errors were encountered: