From 68908993ebd2af459cd0f2ed6ab340bf62fb3e9d Mon Sep 17 00:00:00 2001 From: Djordje Todorovic Date: Mon, 10 Feb 2020 09:49:14 +0100 Subject: [CSInfo] Use isCandidateForCallSiteEntry() when updating the CSInfo Use the isCandidateForCallSiteEntry(). This should mostly be an NFC, but there are some parts ensuring the moveCallSiteInfo() and copyCallSiteInfo() operate with call site entry candidates (both Src and Dest should be the call site entry candidates). Differential Revision: https://reviews.llvm.org/D74122 --- llvm/lib/CodeGen/MachineOutliner.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'llvm/lib/CodeGen/MachineOutliner.cpp') diff --git a/llvm/lib/CodeGen/MachineOutliner.cpp b/llvm/lib/CodeGen/MachineOutliner.cpp index 46a6e86..8fd3679 100644 --- a/llvm/lib/CodeGen/MachineOutliner.cpp +++ b/llvm/lib/CodeGen/MachineOutliner.cpp @@ -1260,7 +1260,7 @@ bool MachineOutliner::outline(Module &M, MOP.getReg(), true, /* isDef = true */ true /* isImp = true */)); } - if (MI.isCall()) + if (MI.isCandidateForCallSiteEntry()) MI.getMF()->eraseCallSiteInfo(&MI); }; // Copy over the defs in the outlined range. -- cgit v1.1