]> Cypherpunks repositories - gostls13.git/commit
internal/pkgbits: explain the rationale for reference tables
authorMark Freeman <mark@golang.org>
Thu, 22 May 2025 15:06:23 +0000 (11:06 -0400)
committerGopher Robot <gobot@golang.org>
Thu, 29 May 2025 18:47:07 +0000 (11:47 -0700)
commitf14f3aae1c3dc382c15d9c3174a037b7d3595009
treea46d109a9b3789c29f9222211c9858ee34312917
parent4878b4471bf1267a8f87b40ed49b36ab82b79d18
internal/pkgbits: explain the rationale for reference tables

The primary benefit of reference tables is to the linker, though they
are also reasonably compact as compared to absolute element indices. It
is worth also checking if reference table structure is similarly
exploited past the IR linking stage.

Ideally, the reference table definition would live in / near the linker.
As it stands, it's a bit hard to infer the purpose of the reference
tables when looking at pkgbits in isolation.

Change-Id: I496aca5a4edcf28e66fa7863ddfa4d825e1b2e89
Reviewed-on: https://go-review.googlesource.com/c/go/+/675596
Auto-Submit: Mark Freeman <mark@golang.org>
Reviewed-by: Robert Griesemer <gri@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
src/internal/pkgbits/reloc.go