aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Transforms/Utils/SampleProfileLoaderBaseUtil.cpp
diff options
context:
space:
mode:
authorVictor Huang <wei.huang@ibm.com>2021-02-16 21:29:07 +0000
committerVictor Huang <wei.huang@ibm.com>2021-02-16 21:32:16 +0000
commitde3a485d9c391c44e2c90f79bbf8ac13d49d9fb6 (patch)
tree737903bc595113481d95afbdb86aa63e90960879 /llvm/lib/Transforms/Utils/SampleProfileLoaderBaseUtil.cpp
parent9f38001bf07252bc29671cf49b42351f34172dea (diff)
downloadllvm-de3a485d9c391c44e2c90f79bbf8ac13d49d9fb6.zip
llvm-de3a485d9c391c44e2c90f79bbf8ac13d49d9fb6.tar.gz
llvm-de3a485d9c391c44e2c90f79bbf8ac13d49d9fb6.tar.bz2
[NFC][PPC] Refactor TOC representation to allow several entries for the same symbol
We currently represent TOC entries by an MCSymbol. This is not enough in some situations. For example, when accessing an initialized TLS variable v on AIX using the general dynamic model, we need to generate the two following entries for v: .tc .v[TC],v@m .tc v[TC],v One is for the region handle (with the @m relocation), the other is for the variable offset. This refactoring allows storing several entries for the same symbol with different VariantKind in the TOC. If the VariantKind is not specified, we default to VK_None. The AIX TLS implementation using this refactoring to generate the two entries will be posted in a subsequent patch. Patched By: bsaleil Reviewed By: sfertile Differential Revision: https://reviews.llvm.org/D96346
Diffstat (limited to 'llvm/lib/Transforms/Utils/SampleProfileLoaderBaseUtil.cpp')
0 files changed, 0 insertions, 0 deletions