[cfe-dev] Automatic scan-build on the LLVM toolchain

[Sylvestre Ledru]

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 [1], 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 [3]. 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.
Or a wish to have compiler-rt checked with scan-build (while still using the
just-built clang)


>>
>> This work is done through the Debian/LLVM jenkins instance [2].
>> 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.

Sylvestre