[cfe-dev] Code coverage of llvm, clang, lldb & polly
dpeixott at codeaurora.org
Tue May 28 09:27:40 PDT 2013
The polly-test target was recently renamed to check-polly to follow the
convention in other llvm projects:
-- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted
by The Linux Foundation
> -----Original Message-----
> From: llvm-commits-bounces at cs.uiuc.edu [mailto:llvm-commits-
> bounces at cs.uiuc.edu] On Behalf Of Sylvestre Ledru
> Sent: Tuesday, May 28, 2013 8:36 AM
> To: Tobias Grosser
> Cc: lldb-dev at cs.uiuc.edu; llvm-commits at cs.uiuc.edu; cfe-dev at cs.uiuc.edu
> Subject: Re: [cfe-dev] Code coverage of llvm, clang, lldb & polly
> Le 28/05/2013 16:56, Tobias Grosser a écrit :
> > On 05/17/2013 08:09 AM, Sylvestre Ledru wrote:
> >> Hello,
> >> Plugged in the Jenkins instance used to build Debian & Ubuntu nightly
> >> package, I configured a code coverage tool (lcov) with all the tests
> >> of these projects.
> >> Results are published here:
> >> http://buildd-clang.debian.net/coverage/
> > I just looked again at the polly numbers and it seems they are not
> > shown any more. Did anything change recently?
> Did you change anything lately on the test with the autotools ?
> cd build-llvm/ && /usr/bin/make polly-test -C tools/polly/test/ || true
> make: Entering directory `/tmp/buildd/llvm-toolchain-snapshot-
> make: *** No rule to make target `polly-test'. Stop.
> Full log:
> (it is quite big)
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
More information about the cfe-dev