[llvm] [ValueTracking] Make the MaxAnalysisRecursionDepth overridable (PR #137721)

[Ramkumar Ramachandra via llvm-commits]

artagnon wrote:

> Sounds like you're planning on changing the implementation s.t. clients of computeKnownBits should specify the recurison depth max. Wouldn't this create an explosion of tuneable parameters? Is #142384 the start of this effort?

Actually, no: the plan is to strip the parameter altogether, by fixing the underlying issue with a fresh KnownBitsAnalysis with an invalidation strategy. It's going to be a major investment, but I think it will solve all our issues once and for all. #142384 is the start of this effort. I thought about the problem some more after my previous comment.
 
> I'm trying to gauge whether or not I should abandon this PR.

I think so. The Depth parameter is a hack, and we're crippled by its limitations. Rather than an ad-hoc solution, my proposal is to fix it once and for all.

https://github.com/llvm/llvm-project/pull/137721