-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: internal compiler error: missing import reader for cc.noder.Position #49016
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
Comments
Sorry I don't have a smaller repro, I haven't dug in yet to try and see where this is happening. Maybe related to #48454? |
I didn't get the actual test to run completely successfully in Go 1.17 (see below, some module dependency error?), but I confirmed that 'go test -c' works fine, whereas 'go test -c' fails with the above error in Go 1.18. So, this confirms that the test does not include any parameterized types or functions (as expected, but just to be clear). Maybe this relates to some changes that we have made in crawler.go or in the export format in the Go 1.18 timeframe? Will have to dig some more. Error message when running test with Go 1.17:
execute bin/go ["mod" "init" "example.com/ccgo/v3/lib/compcert"] in /tmp/ccgo-test-1543161118 |
This starts failing since https://go-review.googlesource.com/c/go/+/327871 The problem is that in https://go-review.googlesource.com/c/go/+/327872, we fixed crawling of embeddable types, so CL 327871 unconditionally call inline.InlineCalls inside methodWrapper. But the I'm going to submit a CL to fix this. |
Change https://golang.org/cl/356254 mentions this issue: |
@danscales Failures with 1.17 may need more digging into, sometimes local config is needed. @cuonglm Tried your CL and was able to |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
No
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: