Sanjay Patel 042574c236 [ValueTracking] define/use max recursion depth in header ... There's a potential motivating case to increase this limit in PR47191: http://bugs.llvm.org/PR47191 But first we should make it less hacky. The limit in InstCombine is directly tied to this value because an increase there can cause asserts in the underlying value tracking calls if not changed together. The usage in VectorUtils is independent, but the comment suggests that we should use the same value unless there's a known reason to diverge. There are similar limits in codegen analysis, but I think we should leave those independent in case we intentionally want the optimization power/cost to be different there. Differential Revision: https://reviews.llvm.org/D86113		2020-08-19 16:56:59 -04:00
..
llvm	[ValueTracking] define/use max recursion depth in header	2020-08-19 16:56:59 -04:00
llvm-c	Recommit "[IPConstProp] Remove and move tests to SCCP."	2020-08-02 22:23:54 +01:00