aboutsummaryrefslogtreecommitdiff
path: root/llvm/utils/TableGen/X86DisassemblerTables.cpp
diff options
context:
space:
mode:
authorMircea Trofin <mtrofin@google.com>2024-08-02 20:51:27 -0400
committerGitHub <noreply@github.com>2024-08-02 20:51:27 -0400
commitba4da5a087f28c9522bc7f173e99673bb3009af9 (patch)
tree92b87009e6bbe820860cc936e9ffd1cfe284337a /llvm/utils/TableGen/X86DisassemblerTables.cpp
parentac319a8dd8b7999ffa0342e50e02932c5c8f7a6a (diff)
downloadllvm-ba4da5a087f28c9522bc7f173e99673bb3009af9.zip
llvm-ba4da5a087f28c9522bc7f173e99673bb3009af9.tar.gz
llvm-ba4da5a087f28c9522bc7f173e99673bb3009af9.tar.bz2
[ctx_prof] "Use" support for pre-thinlink. (#101338)
There is currently no plan to support contextual profiling use in a non- ThinLTO scenario. In the pre-link phase, we only instrument and then immediately bail out to let the linker group functions under an entrypoint in the same module as the entrypoint. We don't actually care what the profile contains - just that we want to use a contextual profile. After that, in post-thinlink, we require the profile be passed again so we can actually use it. The earlier instrumentation will be used to match counter values. While the feature is in development, we add a hidden flag for the use scenario, but we can eventually tie it to the `PGOOptions` mechanism. We will use the same flag in both pre- and post-thinlink, because it simplifies things - usually the post-thinlink args are the same as the ones for pre-. This, despite the flag being basically treated as a boolean in pre-thinlink.
Diffstat (limited to 'llvm/utils/TableGen/X86DisassemblerTables.cpp')
0 files changed, 0 insertions, 0 deletions