forked from OSchip/llvm-project
[ValueTracking] Lower dom-conditions-dom-blocks and dom-conditions-max-uses thresholds
On some of our benchmarks this change shows about 50% compile time improvement without any noticeable performance difference. Differential Revision: http://reviews.llvm.org/D13248 llvm-svn: 248801
This commit is contained in:
parent
a4d3217e81
commit
cea9ede74e
|
@ -58,12 +58,12 @@ static cl::opt<unsigned> DomConditionsMaxDepth("dom-conditions-max-depth",
|
|||
/// conditions?
|
||||
static cl::opt<unsigned> DomConditionsMaxDomBlocks("dom-conditions-dom-blocks",
|
||||
cl::Hidden,
|
||||
cl::init(20000));
|
||||
cl::init(20));
|
||||
|
||||
// Controls the number of uses of the value searched for possible
|
||||
// dominating comparisons.
|
||||
static cl::opt<unsigned> DomConditionsMaxUses("dom-conditions-max-uses",
|
||||
cl::Hidden, cl::init(2000));
|
||||
cl::Hidden, cl::init(20));
|
||||
|
||||
// If true, don't consider only compares whose only use is a branch.
|
||||
static cl::opt<bool> DomConditionsSingleCmpUse("dom-conditions-single-cmp-use",
|
||||
|
|
Loading…
Reference in New Issue