[PATCH] D34277: [analyzer] Bump default performance thresholds?

Artem Dergachev via Phabricator via cfe-commits cfe-commits at lists.llvm.org
Fri Jun 16 13:28:16 PDT 2017

NoQ added a comment.

This was an mixture of internal apple projects (user apps, drivers, deamons, whatever) with a relatively balanced selection of languages and levels of analyzer adoption. They amounted to ~16 hours of analysis CPU time (i.e. 4 hours on a quad-core machine per run). I've also ran it on LLVM separately, and had similar observations. I'm totally welcoming the feedback from other codebases!

In https://reviews.llvm.org/D34277#782605, @zaks.anna wrote:

> > Maybe we should introduce another UMK_* for deeper analysis instead?
> The difference here is not substantial enough to warrant a new level. The general motivation for bumping these numbers is that we've set the timeouts many years ago and the hardware improved quite a bit since then.

Yeah, the point was mostly about default settings, for people who don't bother to tweak them, and adding more options essentially defeats the purpose.


More information about the cfe-commits mailing list