-
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: compiler crashes in ssa: isNonNegative bad type #40746
Comments
Thanks for reporting! When you have a stand-alone test case, even if it's not fully minimized, please do share it. If you need help narrowing things down, let me know. E.g. if you modify the compiler to print v.Block.Func.Name just before the panic, that should let you get down to a single function quickly. |
Hopefully this is small enough, but I think it can be reduced further if necessary. |
That’s great, thanks! We can take it from here. |
Change https://golang.org/cl/248397 mentions this issue: |
@gopherbot please open a backport issue for 1.14. This is a compiler crash on valid input, with no obvious workaround. |
Backport issue(s) opened: #40772 (for 1.14). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
@josharian Does this also need to be backported to 1.15? Now that 1.15 is out, the 1.15 release branch gets separate backport issues too. Thanks. |
Thanks. That was a mistake on my part. Only 1.15 needs it. |
Change https://golang.org/cl/248401 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
The go 1.15 compiler crashes with
What did you expect to see?
My program compiles fine with go 1.14.7, go 1.15 should work the same.
At the moment I cannot reduce my program to something small enough to include in this bug report, I am still working on that so I will update this bug with a reproducing test case. I have run git bisect on the golang git however and found the issue is due to
The text was updated successfully, but these errors were encountered: