From 51891f2364054225b0867009420a2be9603264e8 Mon Sep 17 00:00:00 2001 From: Wei Mi Date: Tue, 19 May 2015 16:09:11 +0000 Subject: [PATCH] Remove the InstructionSimplifierPass immediately after InstructionCombiningPass. InstructionCombiningPass was added after LoopUnrollPass in r237395. Because InstructionCombiningPass is strictly more powerful than InstructionSimplifierPass, remove the unnecessary InstructionSimplifierPass. Differential Revision: http://reviews.llvm.org/D9838 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@237702 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/Transforms/IPO/PassManagerBuilder.cpp | 4 ---- 1 file changed, 4 deletions(-) diff --git a/lib/Transforms/IPO/PassManagerBuilder.cpp b/lib/Transforms/IPO/PassManagerBuilder.cpp index 3b21d3f0cb1..3496a663f53 100644 --- a/lib/Transforms/IPO/PassManagerBuilder.cpp +++ b/lib/Transforms/IPO/PassManagerBuilder.cpp @@ -385,10 +385,6 @@ void PassManagerBuilder::populateModulePassManager( // LoopUnroll may generate some redundency to cleanup. MPM.add(createInstructionCombiningPass()); - // This is a barrier pass to avoid combine LICM pass and loop unroll pass - // within same loop pass manager. - MPM.add(createInstructionSimplifierPass()); - // Runtime unrolling will introduce runtime check in loop prologue. If the // unrolled loop is a inner loop, then the prologue will be inside the // outer loop. LICM pass can help to promote the runtime check out if the