-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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: bad live variable at entry (part 2) #29218
Comments
Tentatively marking as a 1.12 release blocker since it's a new compiler crash on a small and somewhat reasonable program, but leaving to @randall77 to decide if it's ok. |
It looks like the infinite loop makes it so that the end of the memory state chain is never used, so the entire memory chain is dead-code eliminated. That chain includes VARDEFs for some variables that still have an LEAQ for them. That makes the variables look live on entry. I'm going to remove release blocker. This can only happen for infinite loops with no reads or writes in them. That seems unlikely to ever happen in real code. At least, non-buggy real code. |
Change https://golang.org/cl/176498 mentions this issue: |
Change https://golang.org/cl/177140 mentions this issue: |
Change https://golang.org/cl/179098 mentions this issue: |
The following program
crashes the tip compiler with:
It compiles fine on go1.11.
The crash looks similar to the one in #28445, but the toolchain I'm fuzzing includes the fix for that one.
The text was updated successfully, but these errors were encountered: