Go: runtime: performance regression about 2~3ms since Go 1.15 on macOS, due to linking two more shared libraries [1.15 backport]

[gopherbot]

@FiloSottile requested issue #40727 to be considered for backport to the next 1.15 minor release.

@gopherbot please open a backport issue for Go 1.15.

I am not sure this qualifies to be backported, but it might as it's a regression with no workaround.

The team will evaluate it in the backport issue.

[randall77]

I vote against backporting this. It's 3ms extra time on process startup, which doesn't seem serious enough to warrant a backport.

[itchyny]

The 3ms extra time seems to be based the original issue, so if you judge whether or not backport based on the overhead amount, would you benchmark and reevaluate the overhead please?

[networkimprov]

Possibly related: #40781

[networkimprov]

Backport posted:

Change https://golang.org/cl/248719 mentions this issue: [release-branch.go1.15] cmd/link: link dynamic library automatically

cc @cherrymui

[cherrymui]

I made a CL anyway, but feel free to reject (or accept).

[dmitshur]

We have discussed this backport request in a release meeting, and decided this issue does not meet the bar for being backported to Go 1.15. The fix for this issue will be available in Go 1.16.