[PATCH] D31137: [Inliner] Update Inliner code not to subtract CallPenalty twice
Evgeny Astigeevich via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Wed Mar 22 05:14:19 PDT 2017
This revision was automatically updated to reflect the committed changes.
Closed by commit rL298496: r286814 resulted that CallPenalty can be subtracted twice: (authored by eastig).
Changed prior to commit:
https://reviews.llvm.org/D31137?vs=92342&id=92621#toc
Repository:
rL LLVM
https://reviews.llvm.org/D31137
Files:
llvm/trunk/lib/Transforms/IPO/Inliner.cpp
Index: llvm/trunk/lib/Transforms/IPO/Inliner.cpp
===================================================================
--- llvm/trunk/lib/Transforms/IPO/Inliner.cpp
+++ llvm/trunk/lib/Transforms/IPO/Inliner.cpp
@@ -289,7 +289,7 @@
// treating them as truly abstract units etc.
TotalSecondaryCost = 0;
// The candidate cost to be imposed upon the current function.
- int CandidateCost = IC.getCost() - (InlineConstants::CallPenalty + 1);
+ int CandidateCost = IC.getCost() - 1;
// This bool tracks what happens if we do NOT inline C into B.
bool callerWillBeRemoved = Caller->hasLocalLinkage();
// This bool tracks what happens if we DO inline C into B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D31137.92621.patch
Type: text/x-patch
Size: 671 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170322/67d61a71/attachment.bin>
More information about the llvm-commits
mailing list