all: give nested modules fully-qualified names

2023-01-30T15:19:45Z

The two crypto modules are both named "asm". If both are included in a single go.work (e.g., from `go work use -r .` in the repo), builds break from "module asm appears multiple times in workspace". Give these modules fully-qualified names to avoid conflicts. While we are here, also expand the name of two other testdata modules. Those modules don't currently conflict, but they have vague names at risk of future conflicts. Fixes #57769. Change-Id: I2bd8a505051e92348d49560ec698ed921f2c81be Reviewed-on: https://go-review.googlesource.com/c/go/+/461896 Reviewed-by: Bryan Mills TryBot-Result: Gopher Robot Reviewed-by: Filippo Valsorda Run-TryBot: Michael Pratt Reviewed-by: Cherry Mui Auto-Submit: Michael Pratt

cmd/internal/objfile: correct file table reading for Go object file

2020-10-16T14:40:50Z

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 Run-TryBot: Cherry Zhang TryBot-Result: Go Bot Reviewed-by: Than McIntosh Reviewed-by: Jeremy Faller

go/src/cmd/objdump/testdata/testfilenum, branch makepkg

all: give nested modules fully-qualified names

cmd/internal/objfile: correct file table reading for Go object file