Wei Mi eafb39b656 [SCEV] Try to reuse existing value during SCEV expansion ... Current SCEV expansion will expand SCEV as a sequence of operations and doesn't utilize the value already existed. This will introduce redundent computation which may not be cleaned up throughly by following optimizations. This patch introduces an ExprValueMap which is a map from SCEV to the set of equal values with the same SCEV. When a SCEV is expanded, the set of values is checked and reused whenever possible before generating a sequence of operations. The original commit triggered regressions in Polly tests. The regressions exposed two problems which have been fixed in current version. 1. Polly will generate a new function based on the old one. To generate an instruction for the new function, it builds SCEV for the old instruction, applies some tranformation on the SCEV generated, then expands the transformed SCEV and insert the expanded value into new function. Because SCEV expansion may reuse value cached in ExprValueMap, the value in old function may be inserted into new function, which is wrong. In SCEVExpander::expand, there is a logic to check the cached value to be used should dominate the insertion point. However, for the above case, the check always passes. That is because the insertion point is in a new function, which is unreachable from the old function. However for unreachable node, DominatorTreeBase::dominates thinks it will be dominated by any other node. The fix is to simply add a check that the cached value to be used in expansion should be in the same function as the insertion point instruction. 2. When the SCEV is of scConstant type, expanding it directly is cheaper than reusing a normal value cached. Although in the cached value set in ExprValueMap, there is a Constant type value, but it is not easy to find it out -- the cached Value set is not sorted according to the potential cost. Existing reuse logic in SCEVExpander::expand simply chooses the first legal element from the cached value set. The fix is that when the SCEV is of scConstant type, don't try the reuse logic. simply expand it. Differential Revision: http://reviews.llvm.org/D12090 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@259736 91177308-0d34-0410-b5e6-96231b3b80d8		2016-02-04 01:27:38 +00:00
..
Hello	Remove autoconf support	2016-01-26 21:29:08 +00:00
InstCombine	[InstCombine] Revert r238452: Fold IntToPtr and PtrToInt into preceding loads.	2016-02-03 18:04:13 +00:00
Instrumentation	[InstrProfiling] Fix a comment (NFC)	2016-02-03 23:22:43 +00:00
IPO	LowerBitSets: Don't bother to do any work if the llvm.bitset.test intrinsic is unused.	2016-02-03 03:48:46 +00:00
ObjCARC	Add support for objc_unsafeClaimAutoreleasedReturnValue to the	2016-01-27 19:05:08 +00:00
Scalar	[LoopStrengthReduce] Don't rewrite PHIs with incoming values from CatchSwitches	2016-02-03 21:30:34 +00:00
Utils	[SimplifyCFG] Fix for "endless" loop after dead code removal (Alternative to	2016-02-03 23:54:25 +00:00
Vectorize	[SCEV] Try to reuse existing value during SCEV expansion	2016-02-04 01:27:38 +00:00
CMakeLists.txt
LLVMBuild.txt