[ThinLTO] Don't emit original GUID for locals to distributed indexes
authorTeresa Johnson <tejohnson@google.com>
Wed, 22 Sep 2021 23:25:33 +0000 (16:25 -0700)
committerTeresa Johnson <tejohnson@google.com>
Fri, 24 Sep 2021 00:35:47 +0000 (17:35 -0700)
commit2c1defeee40cf643ea6f0fa5e01164c9a4c48c30
tree65b557ac9ee027e14b1230fbe3799d6f1e68959c
parentc579c658cd42034449d4fa19f28b43f2082c0991
[ThinLTO] Don't emit original GUID for locals to distributed indexes

In ThinLTO for locals we normally compute the GUID from the name after
prepending the source path to get a unique global id. SamplePGO indirect
call profiles contain the target GUID without this uniquification,
however (unless compiling with -funique-internal-linkage-names).
Therefore, the index contains the original GUID of the local symbols
(without module path prepended to uniquify), in order to correctly
handle the call edges added for these indirect call profile targets
with SamplePGO.

We were emitting these to the combined index when writing it out as
bitcode, which is unnecessary and causes overhead when writing out the
indexes for distributed backends. The only use of the original GUID name
is in the thin link. Suppress it in that case. This reduced the thin
link time for a large distributed build by about 7%, and the aggregate
size of the serialized indexes by over 2%.

Continue to print it when writing out the full index, since that is just
used for debugging and testing.

Update a distributed thinlto index test to contain a local and ensure
that we don't get a COMBINED_ORIGINAL_NAME record.

Differential Revision: https://reviews.llvm.org/D110296
llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
llvm/test/ThinLTO/X86/distributed_indexes.ll