-
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
x/tools/go/ssa: panic: T #54274
Comments
CC @timothy-king, @findleyr. |
What is the output of |
As you are on bazel the previous request for I suspect you are compiling against a too old version. This is very similar to #54086 |
It is the version in |
I am not able to reproduce this. Without being able to reproduce this my suspicion is still that your nogo binary has not been built using an up to date golang.org/x/tools (such as v0.1.11) FWIW. Are you sure it is up to date? (Also how are you sure? This might help me.) Here is what I have tried so far. I bootstrapped bazel, created a blaze workspace with nogo analysis (using v0.34 of rules_go), created a mildly custom analyzer to inspect the ssa, created an example with features that should tickle this, and ran nogo on the example.
I think I need more specific reproduction instructions at this point. Code under analysis? Blaze+nogo setup? --- hello.go
--- WORKSPACE
--- BUILD.bazel
--- printbuildinfo.go
FWIW
|
@timothy-king you were right. My other Bazel config was downgrading |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
I'm using v0.34 of
bazelbuild/rules_go
's nogo functionality. This includes v0.1.11 ofgolang.org/x/tools
. When I use eithergolang.org/x/tools/go/analysis/passes/nilness
orgolang.org/x/tools/go/analysis/passes/unusedwrite
, I get a panic. I looked through all of the commits since v0.1.11 and none of them look like they would fix the issue. It would be difficult for me to test a newer version though.Sample nilness panic
Sample unusedwrite panic
The text was updated successfully, but these errors were encountered: