cmd/link: remove dependencies on cmd/internal/obj

[mdempsky]

cmd/internal/obj is for writing Go object files, whereas cmd/link only reads Go object files. We should remove cmd/link's dependencies on cmd/internal/obj by moving legitimately shared constants/types into separate packages.

See also #14782.

[davecheney]

Yes please.

On Thu, Apr 7, 2016 at 3:09 PM, Matthew Dempsky [email protected]
wrote:

cmd/internal/obj is for writing Go object files, whereas cmd/link only
reads Go object files. We should remove cmd/link's dependencies on
cmd/internal/obj by moving legitimately shared constants/types into
separate packages.

See also #14782 #14782.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#15165

[mwhudson]

Concur. I even wonder about de-coupling the constants used for LSym.Type between cmd/internal/obj and the linker -- the latter uses far more. The code to read them from object files could map from the obj.Type to the ld.Type. Or something -- currently the constant definitions in obj "know" way too much about the guts of the linker. (It doesn't help that the linker depends on the order these constants sort in)

[gopherbot]

CL https://golang.org/cl/21644 mentions this issue.