search for: sourcebasedcodecoverage

...s to pass this checking, I still get other errors. So my problem is whether llvm-cov has to work with MCAssembler and is it possible to do it with binutils? Coverage support should be / is largely compatible with binutils, but you may have to watch out for this BFD bug: https://clang.llvm.org/docs/SourceBasedCodeCoverage.html#drawbacks-and-limitations What is the error you see? vedant Best, Ruobin -----邮件原件----- 发件人: vsk at apple.com<mailto:vsk at apple.com> [mailto:vsk at apple.com] 发送时间: 2019年1月23日 1:24 收件人: xuruobin <xuruobin at huawei.com<mailto:xuruobin at huawei.com>> 抄送: llvm-dev at...

...21 PM, xuruobin via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > > > Hi all, > > > > I'm trying to support llvm-cov for a new architecture and I have successfully > built compiler-rt for my arch. Following steps shown in > https://clang.llvm.org/docs/SourceBasedCodeCoverage.html , I encountered > an error for the last step(step of llvm-cov show). > > The command line was (supposed my arch is XXXX) > > > > "llvm-cov show -arch=XXXX ./foo -instr-profile=foo.profdata" > > > > and the error was > > > > "Failed to...

Hi all, I'm trying to support llvm-cov for a new architecture and I have successfully built compiler-rt for my arch. Following steps shown in https://clang.llvm.org/docs/SourceBasedCodeCoverage.html , I encountered an error for the last step(step of llvm-cov show). The command line was (supposed my arch is XXXX) "llvm-cov show -arch=XXXX ./foo -instr-profile=foo.profdata" and the error was "Failed to load coverage: No object file for requested architecture." I thi...

...s to pass this checking, I still get other errors. So my problem is whether llvm-cov has to work with MCAssembler and is it possible to do it with binutils? Coverage support should be / is largely compatible with binutils, but you may have to watch out for this BFD bug: https://clang.llvm.org/docs/SourceBasedCodeCoverage.html#drawbacks-and-limitations What is the error you see? vedant Best, Ruobin -----邮件原件----- 发件人: vsk at apple.com<mailto:vsk at apple.com> [mailto:vsk at apple.com] 发送时间: 2019年1月23日 1:24 收件人: xuruobin <xuruobin at huawei.com<mailto:xuruobin at huawei.com>> 抄送: llvm-dev a...

...-gcov-branch-coverage-with-c-producing-branches-all-over-the-place>). Instead, I turn to use clang and the 'source-based code coverage' feature may be a right choice. But i can't find anything to describe branch coverage explicitly on the official site <https://clang.llvm.org/docs/SourceBasedCodeCoverage.html>. So how to use clang to get branch coverage by utilizing 'source-based...' feature? And is *region coverage *equivalent to branch coverage? (I tested on a simple program and region coverage seems pretty close to branch coverage) Any help is highly appreciated Thanks, Ted Xie --...

Hi , I could see the LLVM code coverage info at the below links http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html http://llvm.org/reports/coverage/ I am interested in the branch coverage metric. I could not find the branch coverage related info . Can anyone let me know how to find it. If it is not available , I am happy to work on it, if I can get some details on why

Hi all, I'm now working on llvm-cov for a new target and have a problem here. Because of some reasons, users do not stub in the main function and after running elf file, they cannot get a default profraw. Now they want to construct a default profraw manually but don't know how data is laid out in `default profraw` file. We found a struct ProfDataIOVec in InstrProfilingWriter.c in

..."+-fcoverage-mapping +-fprofile-instr-generate=/tmp/opt_%m.profraw" * Rebuild ("ninja opt" again). This will enable coverage instrumentation, but only for the files you've affected with your changes. * Run a one-liner to generate a coverage report (http://clang.llvm.org/docs/SourceBasedCodeCoverage.html#creating-coverage-reports <http://clang.llvm.org/docs/SourceBasedCodeCoverage.html#creating-coverage-reports>) I like this approach because it means I don't have to maintain a separate, coverage-enabled build tree. It's an easy way to check that your patches have decent test cov...

...h-c-producing-branches-all-over-the-place>). > Instead, I turn to use clang and the 'source-based code coverage' feature > > may be a right choice. But i can't find anything to describe branch > coverage explicitly on the official site > <https://clang.llvm.org/docs/SourceBasedCodeCoverage.html>. > > > > So how to use clang to get branch coverage by utilizing 'source-based...' > feature? And is *region coverage *equivalent to branch coverage? > > (I tested on a simple program and region coverage seems pretty close to > branch coverage) > > &g...

...mapping +-fprofile-instr-generate=/tmp/opt_%m.profraw" >> * Rebuild ("ninja opt" again). This will enable coverage instrumentation, but only for the files you've affected with your changes. >> * Run a one-liner to generate a coverage report (http://clang.llvm.org/docs/SourceBasedCodeCoverage.html#creating-coverage-reports <http://clang.llvm.org/docs/SourceBasedCodeCoverage.html#creating-coverage-reports>) >> >> I like this approach because it means I don't have to maintain a separate, coverage-enabled build tree. It's an easy way to check that your patches ha...

Hi, I'd like to track not just at the function level, but also at the code block level. For example, for a if-else statement, I want to know when the if-branch or else-branch is enter/exit. Is there a clang option similar to -finstrument-functions for code blocks? Alternatively, I could manually insert the code to the IR .ll file. I see the generated .ll use the following function when

+ Vedant Hi Hal, thanks. I apologize if my answers aren't as thorough as you would like; what I'm proposing is simply an extension to the existing infrastructure, so it would be enabled automatically as part of code coverage. Mapping of branch regions would be done in CoverageMappingGen and instrumented using the same profiling instrumentation mechanism under

...h-c-producing-branches-all-over-the-place>). > Instead, I turn to use clang and the 'source-based code coverage' feature > > may be a right choice. But i can't find anything to describe branch > coverage explicitly on the official site > <https://clang.llvm.org/docs/SourceBasedCodeCoverage.html>. > > > > So how to use clang to get branch coverage by utilizing 'source-based...' > feature? And is *region coverage *equivalent to branch coverage? > > (I tested on a simple program and region coverage seems pretty close to > branch coverage) > > &g...

Thanks Vedant, and my apologies for the delay getting back to you - work got "busy". I wasn't aware of the '-fprofile-generate' option, so thanks for point this out. I have tried running it and I can see the instrumentation hooks that it generates - I assume that there is a library I have to implement to support this, can you let me know where the source for this library

On Wed, Oct 25, 2017 at 09:13:54AM -0700, Xinliang David Li wrote: > On Wed, Oct 25, 2017 at 12:26 AM, Roger Pau Monné via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > Hello, > > > > I've been working on implementing some basic functionality in order to > > use the llvm profiling functionality inside of a kernel (the Xen > > hypervisor).

Introduce the functionality in order to fill the hooks of the cov_sysctl_ops struct. Signed-off-by: Roger Pau Monné <roger.pau at citrix.com> --- Cc: Andrew Cooper <andrew.cooper3 at citrix.com> Cc: George Dunlap <George.Dunlap at eu.citrix.com> Cc: Ian Jackson <ian.jackson at eu.citrix.com> Cc: Jan Beulich <jbeulich at suse.com> Cc: Konrad Rzeszutek Wilk