summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Utils/InstructionNamer.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2016-12-27 01:24:50 +0000
committerChandler Carruth <chandlerc@gmail.com>2016-12-27 01:24:50 +0000
commit0ee8bb11c33fb4bc38d308e4893e4b27fe09b234 (patch)
tree3567926aa341b96b65722d1de99d4a4ecd4e001a /llvm/lib/Transforms/Utils/InstructionNamer.cpp
parentdffe45b3e6553b2ab09ad05a82000a33d3a0d964 (diff)
downloadbcm5719-llvm-0ee8bb11c33fb4bc38d308e4893e4b27fe09b234.tar.gz
bcm5719-llvm-0ee8bb11c33fb4bc38d308e4893e4b27fe09b234.zip
[PM] Move the collection of call sites to a more appropriate place
inside of `InlineFunction`. Prior to this, call instructions are specifically being rewritten and replaced within the inlined region, invalidating some of the call sites. Several of these regions are using the same technique to walk the inlined region so this seems clearly safe up to this point. I've also added a short circuit to the scan for call sites based on what other code is doing. With this, the most common crash I've found in the new inliner code is fixed. I've turned it on for another test case that covers this scenario. I'll make my way through most of the other inliner test cases just to get some easy coverage next. llvm-svn: 290562
Diffstat (limited to 'llvm/lib/Transforms/Utils/InstructionNamer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud