aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2012-04-01 10:41:24 +0000
committerChandler Carruth <chandlerc@gmail.com>2012-04-01 10:41:24 +0000
commitdafe48e230916ce0de4228d81dece732159994f1 (patch)
tree1461f072e17cf5af83397f402a2b1b2e996db8d9
parent48ec3b50e7fae0cdb8c83fb33423cb3e93a6270e (diff)
downloadexternal_llvm-dafe48e230916ce0de4228d81dece732159994f1.zip
external_llvm-dafe48e230916ce0de4228d81dece732159994f1.tar.gz
external_llvm-dafe48e230916ce0de4228d81dece732159994f1.tar.bz2
Belatedly address some code review from Chris.
As a side note, I really dislike array_pod_sort... Do we really still care about any STL implementations that get this so wrong? Does libc++? git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@153834 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--lib/Transforms/IPO/Inliner.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/Transforms/IPO/Inliner.cpp b/lib/Transforms/IPO/Inliner.cpp
index 2d70398..8a9d149 100644
--- a/lib/Transforms/IPO/Inliner.cpp
+++ b/lib/Transforms/IPO/Inliner.cpp
@@ -552,7 +552,7 @@ bool Inliner::removeDeadFunctions(CallGraph &CG, bool AlwaysInlineOnly) {
// Note that it doesn't matter that we are iterating over a non-stable order
// here to do this, it doesn't matter which order the functions are deleted
// in.
- std::sort(FunctionsToRemove.begin(), FunctionsToRemove.end());
+ array_pod_sort(FunctionsToRemove.begin(), FunctionsToRemove.end());
FunctionsToRemove.erase(std::unique(FunctionsToRemove.begin(),
FunctionsToRemove.end()),
FunctionsToRemove.end());