[lldb-dev] [cfe-dev] Automatic scan-build on the LLVM toolchain
dblaikie at gmail.com
Sun Jul 7 09:50:13 PDT 2013
On Jul 7, 2013 6:37 AM, "Sylvestre Ledru" <sylvestre at debian.org> wrote:
> On 06/07/2013 18:11, David Blaikie wrote:
> > On Jul 6, 2013 7:34 AM, "Sylvestre Ledru" <sylvestre at debian.org
> > <mailto:sylvestre at debian.org>> wrote:
> >> Hello,
> >> After setting an automatic code coverage tool , I just plugged an
> >> automatic scan-build on the LLVM toolchain:
> >> http://buildd-clang.debian.net/scan-build/
> >> 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
> > 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.
> Or a wish to have compiler-rt checked with scan-build (while still using
> just-built clang)
I'm not entirely clear on how scan-build works, but I assumed it redefined
cxx and cc to run the analyzer and then run the old value of cxx and cc, so
I'm not sure how the build system for compiler rt would gracefully support
that. The build wants yto set cxx and cc to point to the just built clang,
which overrides the value set by scan-build, losing the interception.
> >> 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/ <http://llvm.org/apt/>.
> > Any reason this can't be a two stage and use the previous build to
> > analyze the next?
> For two main reasons:
> * it is faster (I don't have to build clang during this process)
> * it is easier in the current process of building the package.
> However, I am planning to do it at some point.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev