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/link: panic in deadcode flood #16887
Comments
Is the source of the code you are compiling available so I can try to On Fri, Aug 26, 2016 at 3:15 PM, wangkechun notifications@github.com
|
cc @crawshaw -- the panic is probably from decodetypeKind in this line: if decodetypeKind(s)&kindMask == kindInterface { |
+1. Same error. Trying to build an otherwise working program with go:binary-only-package in official docker. go version go1.7.1 linux/amd64 go env. GOARCH="amd64" |
@mandeepbrar want to try out https://golang.org/cl/29692? It's designed to fix #17140 but the diagnostics change may mean you get further into linking before an error. |
@crawshaw Seems to go a little further, but an error again ` goroutine 1 [running]: ` |
Does anybody have a repro here? I'm going to kick to Go1.10 since we don't have one yet. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Please answer these questions before submitting your issue. Thanks!
go version
)?go version go1.7 darwin/amd64
go env
)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/wkc"
GORACE=""
GOROOT="/Users/wkc/local/go"
GOTOOLDIR="/Users/wkc/local/go/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/xw/mx32d21j5hd_1gyxv14c77m00000gn/T/go-build713088348=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
The text was updated successfully, but these errors were encountered: