aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Transforms/Utils/InlineFunction.cpp
diff options
context:
space:
mode:
authorArthur Eubanks <aeubanks@google.com>2021-07-19 10:32:12 -0700
committerArthur Eubanks <aeubanks@google.com>2021-07-20 10:20:10 -0700
commit6144fc2da1b87dc64ff887d73b60f7708f5cb0a4 (patch)
tree0477bbb3b5411e4ea68cfc96a2865ec323737d6b /llvm/lib/Transforms/Utils/InlineFunction.cpp
parent7704fedfff6ef5676adb6415f3be0ac927d1a746 (diff)
downloadllvm-6144fc2da1b87dc64ff887d73b60f7708f5cb0a4.zip
llvm-6144fc2da1b87dc64ff887d73b60f7708f5cb0a4.tar.gz
llvm-6144fc2da1b87dc64ff887d73b60f7708f5cb0a4.tar.bz2
[NewPM] Print pre-transformation IR name in --print-after-all
Sometimes a transformation can change the name of some IR (e.g. an SCC with functions added/removed). This can be confusing when debug logging doesn't match the post-transformation name. The specific example I came across was that --print-after-all said the inliner was working on an SCC that only contained one function, but calls in multiple functions were getting inlined. After all inlining, the current SCC only contained one function. Piggyback off of the existing logic to handle invalidated IR + --print-module-scope. Simply always store the IR description and use that. Reviewed By: jamieschmeiser Differential Revision: https://reviews.llvm.org/D106290
Diffstat (limited to 'llvm/lib/Transforms/Utils/InlineFunction.cpp')
0 files changed, 0 insertions, 0 deletions