george.karpenkov added a comment. @Szelethus false positives are a single biggest problem of the analyzer. By a *huge* margin, most projects would prefer to err on the side of less, more precise, warnings. Given that currently in my understanding no actual bugs we are sure about were found by the uninitialized object checker, I think by default we should err on the "less warnings" side.
This solves part of the problem, could we also separate the code somehow? Let's say I would need to debug UnitializedObjectChecker without understanding the details of how the pointer chasing is done --- it's hard to do that when all the code is intermixed in one file. Repository: rC Clang https://reviews.llvm.org/D49438 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits