diff options
author | Bjorn Pettersson <bjorn.a.pettersson@ericsson.com> | 2021-07-08 14:24:03 +0200 |
---|---|---|
committer | Bjorn Pettersson <bjorn.a.pettersson@ericsson.com> | 2021-07-09 09:47:03 +0200 |
commit | 472462c4723978db5a09c0058ddec025e6a6a94b (patch) | |
tree | 664dffb5840729ab24cc2db109ecde5efc9fafd4 /llvm/lib/Analysis/InlineCost.cpp | |
parent | e24bb698bb445ee785ad25f53aa76b1242aec217 (diff) | |
download | llvm-472462c4723978db5a09c0058ddec025e6a6a94b.zip llvm-472462c4723978db5a09c0058ddec025e6a6a94b.tar.gz llvm-472462c4723978db5a09c0058ddec025e6a6a94b.tar.bz2 |
[NewPM] Consistently use 'simplifycfg' rather than 'simplify-cfg'
There was an alias between 'simplifycfg' and 'simplify-cfg' in the
PassRegistry. That was the original reason for this patch, which
effectively removes the alias.
This patch also replaces all occurrances of 'simplify-cfg'
by 'simplifycfg'. Reason for choosing that form for the name is
that it matches the DEBUG_TYPE for the pass, and the legacy PM name
and also how it is spelled out in other passes such as
'loop-simplifycfg', and in other options such as
'simplifycfg-merge-cond-stores'.
I for some reason the name should be changed to 'simplify-cfg' in
the future, then I think such a renaming should be more widely done
and not only impacting the PassRegistry.
Reviewed By: aeubanks
Differential Revision: https://reviews.llvm.org/D105627
Diffstat (limited to 'llvm/lib/Analysis/InlineCost.cpp')
-rw-r--r-- | llvm/lib/Analysis/InlineCost.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/lib/Analysis/InlineCost.cpp b/llvm/lib/Analysis/InlineCost.cpp index 4e03629..e73b0fa 100644 --- a/llvm/lib/Analysis/InlineCost.cpp +++ b/llvm/lib/Analysis/InlineCost.cpp @@ -2211,7 +2211,7 @@ bool CallAnalyzer::visitSwitchInst(SwitchInst &SI) { // proportional to the size of the tree or the size of jump table range. // // NB: We convert large switches which are just used to initialize large phi - // nodes to lookup tables instead in simplify-cfg, so this shouldn't prevent + // nodes to lookup tables instead in simplifycfg, so this shouldn't prevent // inlining those. It will prevent inlining in cases where the optimization // does not (yet) fire. |