-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
cmd/compile: unreachable panic with GODEBUG=gotypesalias=1 #65778
Comments
The line in runtime2.go appears to be |
@griesemer I think there's also a problem in types2 and go/types. Running
|
@cuonglm Thanks. I am reproducing this now. |
To clarify, I do think the problem happens with both types2 and the compiler. The last time I look at this, I was able to have a patch for types2 to make It could also be my patch is not good enough and not fixing the root cause in types2. |
|
Yeah, I tried adding that missing piece, and |
Change https://go.dev/cl/565835 mentions this issue: |
Fixes #65854. For #65778. // for x/tools/cmd/gotype Change-Id: I67d4644b28e831926fc6c233098aa1755c57162f Reviewed-on: https://go-review.googlesource.com/c/go/+/565835 Auto-Submit: Robert Griesemer <gri@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Robert Griesemer <gri@google.com>
@gopherbot please consider this for backport to 1.22. It is a panic that prevents tool developers from preparing their tool for go/types Aliases. |
Backport issue(s) opened: #65858 (for 1.22). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Change https://go.dev/cl/565840 mentions this issue: |
Just to be clear, the cherry-pick only addresses the cmd/gotype issue. The compiler crash is still present. |
@mdempsky This still crashes in the compiler front-end somewhere. Assigning to you for now. |
Change https://go.dev/cl/565995 mentions this issue: |
Change https://go.dev/cl/568156 mentions this issue: |
Thanks all for the updates. Happy to try GODEBUG=gotypesalias=1 again on master once the fixes have all landed. |
Similar with what we are doing for -goexperiment. For #65778 Change-Id: I7dda69512a3ffb491e3de31941ae1c3d34fececf Reviewed-on: https://go-review.googlesource.com/c/go/+/568156 Auto-Submit: Cuong Manh Le <cuong.manhle.vn@gmail.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
…itution Fixes #65858. For #65778. // for x/tools/cmd/gotype Change-Id: I67d4644b28e831926fc6c233098aa1755c57162f Reviewed-on: https://go-review.googlesource.com/c/go/+/565835 Auto-Submit: Robert Griesemer <gri@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Robert Griesemer <gri@google.com> Reviewed-on: https://go-review.googlesource.com/c/go/+/565840 Run-TryBot: Robert Griesemer <gri@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
Go version
go version devel go1.23-86a32d6d9c 2024-02-17 06:03:15 +0000 linux/amd64
Output of
go env
in your module/workspace:What did you do?
Clone https://github.com/mvdan/garble-fork at branch go-alias-panic (9e9c6235febfa5a6ea9d87569ea67d4cca0721a9).
What did you see happen?
What did you expect to see?
No failure, just like without
GODEBUG
.I can reproduce by building other modules as well, but I'm just showing one here with a known "bad" commit.
Go 1.22.0 also fails, just with less information:
cc @findleyr @adonovan @griesemer
The text was updated successfully, but these errors were encountered: