[llvm] [CaptureTracking] Raise the default use budget from 100 to 150 (PR #222654)

Nikita Popov via llvm-commits llvm-commits at lists.llvm.org
Thu Sep 10 11:59:38 PDT 2026


nikic wrote:

Compile-time CTMark: https://llvm-compile-time-tracker.com/compare.php?from=eb3aad0e4c85c8ce083648297950aa11c46b27e4&to=24d46117b0a8d334581d03dc2f88aebe31edfa1c&stat=instructions:u
Compile-time llvm-opt-benchmark: https://github.com/dtcxzyw/llvm-opt-benchmark-nightly/pull/1253
Diffs llvm-opt-benchmark: https://github.com/dtcxzyw/llvm-opt-benchmark-nightly/pull/1254

CTMark is about neutral. There is negative impact on llvm-opt-benchmark, 0.1% geomean, but up to 60%. This may be due to second order effects, but would need investigation.

I'm not opposed to increasing this limit, given that the compile-time impact seems to be acceptable. Of course, no matter what limit we pick, there's always be some example that would benefit from it being raised further.

Can you share the IR for your motivating case? I do wonder if there is some way to address it that is limit-independent.

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


More information about the llvm-commits mailing list