-
- Downloads
cmd/internal/objfile: correct file table reading for Go object file
Apparently I never actually understood the new file table in Go object files. The PC value stream actually encodes the file index in the per-CU table. I thought it was indexing into a per-function table, which then contains index to the per-CU table. Remove the extra indirection. Change-Id: I0aea5629f7b3888ebe3a04fea437aa15ce89519e Reviewed-on: https://go-review.googlesource.com/c/go/+/262779 Trust: Cherry Zhang <cherryyz@google.com> Run-TryBot: Cherry Zhang <cherryyz@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by:Than McIntosh <thanm@google.com> Reviewed-by:
Jeremy Faller <jeremy@golang.org>
Showing
- src/cmd/internal/objfile/goobj.go 1 addition, 3 deletionssrc/cmd/internal/objfile/goobj.go
- src/cmd/objdump/objdump_test.go 38 additions, 0 deletionssrc/cmd/objdump/objdump_test.go
- src/cmd/objdump/testdata/testfilenum/a.go 7 additions, 0 deletionssrc/cmd/objdump/testdata/testfilenum/a.go
- src/cmd/objdump/testdata/testfilenum/b.go 7 additions, 0 deletionssrc/cmd/objdump/testdata/testfilenum/b.go
- src/cmd/objdump/testdata/testfilenum/c.go 7 additions, 0 deletionssrc/cmd/objdump/testdata/testfilenum/c.go
- src/cmd/objdump/testdata/testfilenum/go.mod 3 additions, 0 deletionssrc/cmd/objdump/testdata/testfilenum/go.mod
src/cmd/objdump/testdata/testfilenum/a.go
0 → 100644
src/cmd/objdump/testdata/testfilenum/b.go
0 → 100644
src/cmd/objdump/testdata/testfilenum/c.go
0 → 100644
src/cmd/objdump/testdata/testfilenum/go.mod
0 → 100644
Please register or sign in to comment