-
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: internal compiler error: panic: runtime error: invalid memory address or nil pointer dereference #54302
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Comments
cc @golang/compiler |
Minimized repro:
|
@gopherbot Please backport to Go 1.19. This is a regression from Go 1.18. |
This was referenced Aug 5, 2022
Backport issue(s) opened: #54308 (for 1.18), #54309 (for 1.19). 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/421755 mentions this issue: |
jproberts
pushed a commit
to jproberts/go
that referenced
this issue
Aug 10, 2022
The RType field isn't needed when performing type assertions from non-empty interface types, because we use the ITab field instead. But the inline body exporter didn't know to expect this. It's possible we could use a single bool to distinguish whether we're serializing the RType or ITab field, but using two is simpler and seems safer. Fixes golang#54302. Change-Id: I9ddac72784fb2241fee0a0dee30493d868a2c259 Reviewed-on: https://go-review.googlesource.com/c/go/+/421755 TryBot-Result: Gopher Robot <[email protected]> Run-TryBot: Matthew Dempsky <[email protected]> Reviewed-by: Cuong Manh Le <[email protected]> Reviewed-by: Keith Randall <[email protected]> Auto-Submit: Matthew Dempsky <[email protected]> Reviewed-by: Keith Randall <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Installed the binary from https://go.dev/doc/install today:
Does this issue reproduce with the latest release?
Yes. Here is a play link:
https://go.dev/play/p/R_wq9G9RIFV
That pulls in https://github.com/lightstep/otel-launcher-go/tree/main/lightstep/sdk/metric/aggregator/minmaxsumcount, which compiles in 1.18 but not in 1.19
What operating system and processor architecture are you using (
go env
)?go env
OutputThis may be a duplicate of #54243
What did you expect to see?
In 1.18 this package compiles.
What did you see instead?
In 1.19, the error message:
The text was updated successfully, but these errors were encountered: