aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/ModuloSchedule.cpp
diff options
context:
space:
mode:
authorHuan Nguyen <nhuhuan@yahoo.com>2022-06-18 11:38:37 -0700
committerAmir Ayupov <aaupov@fb.com>2022-06-18 11:39:51 -0700
commit543f13c99b1fa87d491f17dc4a9bcead471b3c58 (patch)
tree7285f738b885e72dd10a2a5cee4c53ff5cabf3a5 /llvm/lib/CodeGen/ModuloSchedule.cpp
parent545a71c0d66eb93eb47ad49ec6f91965cca8f137 (diff)
downloadllvm-543f13c99b1fa87d491f17dc4a9bcead471b3c58.zip
llvm-543f13c99b1fa87d491f17dc4a9bcead471b3c58.tar.gz
llvm-543f13c99b1fa87d491f17dc4a9bcead471b3c58.tar.bz2
[BOLT] Allow function entry to be a cold fragment
Allow cold fragment to get new address. Our previous assumption is that a fragment (.cold) is only reached through the main fragment of same function. In addition, .cold fragment must be reached through either (a) direct transfer, or (b) split jump table. For (a), we perform a simple fix-up. For (b), we currently mark all relevant fragments as non-simple. Therefore, there is no need to get new address for .cold fragment. This is not always the case, as function entry can be rarely executed, and is placed in .text.cold segment. Essentially we cannot tell which the source-level function entry is based on hot and cold segments, so we must treat each fragment a function on its own. Therfore, we remove the assertion that a function entry cannot be cold fragment. Test Plan: ``` ninja check-bolt ``` Reviewed By: Amir Differential Revision: https://reviews.llvm.org/D128111
Diffstat (limited to 'llvm/lib/CodeGen/ModuloSchedule.cpp')
0 files changed, 0 insertions, 0 deletions