[cfe-dev] Including ccc-analyzer build warnings in scan-build report

Daniel Dunbar daniel at zuster.org
Fri Oct 17 10:58:50 PDT 2008

Hi Nikita,
This is a good idea and something Ted and I have discussed. I believe that
Ted has the logs so that it is easy to collect the data, but the blocking
issue was how to present this in the UI (there are still a number of cases
where clang emits bogus warnings, sometimes in large numbers). However, it
is something we want to do to increase the visibility of clang's warnings
and hopefully iron out the bogus warnings faster. Mostly we just need
someone to take it on.

 - Daniel

On Mon, Oct 13, 2008 at 11:16 PM, Nikita Zhuk <nikita at zhuk.fi> wrote:

> Currently developers must manually scan the (usually rather verbose)
> output of scan-build to find any build warnings which are given by ccc-
> analyzer during build since they're excluded from the scan-build
> report. Is it be possible to include those build warnings into scan-
> build report?
> - Nikita
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20081017/8d32cb91/attachment.html>

More information about the cfe-dev mailing list