-
Notifications
You must be signed in to change notification settings - Fork 18k
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: crash in type loop detection #44266
Comments
Might be obvious, but I ran a git bisect, this behavior was there all along in 0e85fd7. Changing this line to also check for
I can prepare and send a CL with a test if there's no objection, or could I be missing something in the bigger picture? |
cc @mdempsky |
Change https://golang.org/cl/292149 mentions this issue: |
Change https://golang.org/cl/292469 mentions this issue: |
It looks like @mdempsky and @randall77 are cc'd on the CLs, also cc'ing @griesemer as an owner. This is currently labeled as a release-blocking issue, and is currently blocking the Go 1.16 release today. |
Removed release blocker. This is a compiler crash on an invalid program, which shouldn't block the release. |
Thanks Keith for the status report. In that case I’ll also move this issue to Go1.17, and out of the Go1.16 milestone. |
I believe this issue is already fixed on dev.regabi with golang.org/cl/274294. If this isn't a blocker for Go 1.16, I suggest we wait until dev.regabi is merged to fix this on the main branch. And we can just backport a fix to the Go 1.16 release branch when appropriate. |
Change https://golang.org/cl/292470 mentions this issue: |
Change https://golang.org/cl/292889 mentions this issue: |
Change https://golang.org/cl/292889 mentions this issue: |
dev.regabi was merged to master, so we can close this issue now. |
Thanks, I can confirm the ICE no longer reproduces on tip. Closing, fixed by CL 292709. |
CL 274294 improved findTypeLoop but also fixed a new found bug on master branch. This Cl adds test cases for this. Updates #44266 Change-Id: Ie4a07a3487758a1e4ad2f2847dcde975b10d2a77 Reviewed-on: https://go-review.googlesource.com/c/go/+/292889 Run-TryBot: Cuong Manh Le <cuong.manhle.vn@gmail.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Matthew Dempsky <mdempsky@google.com> Trust: Cuong Manh Le <cuong.manhle.vn@gmail.com>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
No (tested with go1.15.8)
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run this program: https://play.golang.org/p/JghmS05HSAj
What did you expect to see?
The compiler shouldn't crash
What did you see instead?
The text was updated successfully, but these errors were encountered: