[lldb-dev] [cfe-dev] Automatic scan-build on the LLVM toolchain
dblaikie at gmail.com
Sat Jul 6 09:11:14 PDT 2013
On Jul 6, 2013 7:34 AM, "Sylvestre Ledru" <sylvestre at debian.org> wrote:
> After setting an automatic code coverage tool , I just plugged an
> automatic scan-build on the LLVM toolchain:
> Note that:
> * polly is currently not analyzed. I had to disable the build until the
> new version of cloog is available.
> * compiler-rt is not analyzed because it does not respect the CC/CXX
> argument to use the clang built locally . Should I report a bug here?
I'm not sure what bug to report here, if any, compiler-rt deliberately uses
the just-built clang because it has to be in lock-step with it.
This would be one of those times a compilation database, emitted by clang
itself or the build system, would be a better solution than the scan-build
> This work is done through the Debian/LLVM jenkins instance .
> The report is updated twice a day.
> The scan-build/clang used to produce the report is the one published on
> http://llvm.org/apt/. That means that a new feature/fix done on
> scan-build will appear only about a day after on report. As a side
> effect, it tests automatically the packages distributed on llvm.org/apt/.
Any reason this can't be a two stage and use the previous build to analyze
>  http://buildd-clang.debian.net/coverage/
>  Example:
> -fno-exceptions -fPIC -funwind-tables
> -Wall -Werror -O3 -fomit-frame-pointer -m64 -fPIE -fno-builtin
> -gline-tables-only -fno-rtti -DASAN_FLEXIBLE_MAPPING_AND_OFFSET=1 -c -o
>  http://llvm-jenkins.debian.net/
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev