cmd/compile: set itab function pointers at compile time

I noticed that we don't set an itab's function pointers at compile
time. Instead, we currently do it at executable startup.

Set the function pointers at compile time instead. This shortens
startup time. It has no effect on normal binary size. Object files
will have more relocations, but that isn't a big deal.

For PIE there are additional pointers that will need to be adjusted at
load time. There are already other pointers in an itab that need to be
adjusted, so the cache line will already be paged in. There might be
some binary size overhead to mark these pointers. The "go test -c
-buildmode=pie net/http" binary is 0.18% bigger.

Update #20505

Change-Id: I267c82489915b509ff66e512fc7319b2dd79b8f7
Reviewed-on: https://go-review.googlesource.com/44341
Run-TryBot: Keith Randall <khr@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Martin Möhrmann <moehrmann@google.com>

1 files changed, 1 insertions, 8 deletions

diff --git a/src/runtime/iface.go b/src/runtime/iface.go
index 665dbdbc16..1f31bcae6d 100644
--- a/src/runtime/iface.go
+++ b/src/runtime/iface.go
@@ -167,13 +167,6 @@ func itabAdd(m *itab) {
 	}
 }
 
-// Adds m to the set of initial itabs.
-// itabLock must be held.
-func itabAddStartup(m *itab) {
-	m.init() // TODO: remove after CL 44341
-	itabAdd(m)
-}
-
 // init fills in the m.fun array with all the code pointers for
 // the m.inter/m._type pair. If the type does not implement the interface,
 // it sets m.fun[0] to 0 and returns the name of an interface function that is missing.
@@ -230,7 +223,7 @@ func itabsinit() {
 	lock(&itabLock)
 	for _, md := range activeModules() {
 		for _, i := range md.itablinks {
-			itabAddStartup(i)
+			itabAdd(i)
 		}
 	}
 	unlock(&itabLock)