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

[Jeffrey Byrnes via llvm-commits]

jrbyrnes wrote:

> I think it would be preferable if we could count Depth downwards instead of upwards, as many of the APIs already have a depth parameter. Then, we can pass the max-depth, and it would count upward from 0, instead of passing 0 and relying on a hard-coded parameter. I'll work on a patch for this shortly. This would also match the way InstSimplify counts wrt to its Depth parameter.

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 https://github.com/llvm/llvm-project/pull/142384 the start of this effort?

I'm trying to gauge whether or not I should abandon this PR.


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