similar to: [LLVMDev] llvm-cov outputting coverage results as HTML reports

Xinliang David Li via llvm-dev <llvm-dev at lists.llvm.org> writes: > Harlan Haskins has recently submitted a patch (for review) that implements > --format=html for llvm-cov tool. Please take a look at that patch. For reference, the review thread starts here: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160229/336622.html > David > > On Thu, Mar 3, 2016 at

Hi all, Recently I’ve noticed in coverage profiles that llvm_unreachable and the like are considered uncovered because there’s no special behavior in instrumentation to ‘ignore’ noreturn paths. While I don’t necessarily think it’s ideal to ignore all noreturn decls, I think there’s definitely room for some heuristics around ignoring things like llvm_unreachable (perhaps opt-in?). I’m

+ cfe-dev > On Mar 28, 2016, at 1:23 PM, Harlan Haskins via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > Recently I’ve noticed in coverage profiles that llvm_unreachable and the like are considered uncovered because there’s no special behavior in instrumentation to ‘ignore’ noreturn paths. FWIW, Daniel Dunbar and a few others have brought up the lack of a

Hi All, I want to provide a solution that presents code coverage reports that include the aggregated code-counts across many binaries. Our test engineers currently do this using gcov-mode by merged .gcda data files. We can do a similar merge of the .profraw files, so that the many binaries are represented in one .profdata file; However, llvm-cov will only generate reports based on one binary at

Hi all, I was trying to generate lcov test coverage reports for xapian-core but got an out of memory error: $ lcov --capture --directory . --output-file xapian-core.info Capturing coverage data from . Found gcov version: 4.7.3 Scanning . for .gcda files ... Found 270 data files in . Processing bin/xapian-progsrv.gcda Out of memory! These are the steps I followed in xapian-core directory

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, Alan Thanks for making it clear. But I was more confused now :( I tested on a simple program and used both gcov and lcov to get branch coverage. The code and build commands as below: *Example simple.cc* #include <string> // If not comment this line, the branch coverage won't reach to 100% // #include <iostream> int main(int argc, const char* argv[]) { std::string str =

Hi, Alan Really very excited to receive your email and sorry to be slow replying, it has been exceptionally busy over the last few days ;( Your explanation made the problem clear to me. So gcov branch coverage should be called condition coverage and clang region coverage is branch coverage in fact(also known as *decision/C1*), right? And llvm/clang will support all the following coverage

Hi David, In my use case, our test teams want a single html index file that links to an aggregated coverage report that covers an entire code repository. I see that there is a new patch of generating html reports, is there a way to index all of the individual source files into one summary report, where there are many binary files to consider? *> I don't see why a wrapper script (that

Hi, llvm/clang experts I need to get the branch coverage for some testing code. But i found gcov can't give a expected coverage which may count some 'hidden branch' in (See stackoverflow answer <https://stackoverflow.com/questions/42003783/lcov-gcov-branch-coverage-with-c-producing-branches-all-over-the-place>). Instead, I turn to use clang and the 'source-based code

Hello, I have few questions about coverage. Is there any user-facing documentation for clang's "-coverage" flag? The coverage instrumentation seems to happen before asan, and so if asan is also enabled asan will instrument accesses to @__llvm_gcov_ctr. This is undesirable and so we'd like to skip these accesses. Looks like GEP around @__llvm_gcov_ctr have special metadata

All, Here are the latest patches to expreiment with gcov profiler for xen hypervisor. I have tested current patches on Intel i686. System Details: gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) gcov (Ubuntu 4.3.3-5ubuntu4) 4.3.3 Kernel 2.6.28-11-generic Distribution: Ubuntu jaunty 9.04 There are some design issue which i would like to highlight here: 1. To create gcov proc dir user /proc/xen, we are

All, Here are the latest patches to expreiment with gcov profiler for xen hypervisor. I have tested current patches on Intel i686. System Details: gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) gcov (Ubuntu 4.3.3-5ubuntu4) 4.3.3 Kernel 2.6.28-11-generic Distribution: Ubuntu jaunty 9.04 There are some design issue which i would like to highlight here: 1. To create gcov proc dir user /proc/xen, we are

Another question is about the performance of coverage's at-exit actions (dumping coverage data on disk). I've built chromium's base_unittests with -fprofile-arcs -ftest-coverage and the coverage's at-exit hook takes 22 seconds, which is 44x more than I am willing to pay. Most of the time is spent here: #0 0x00007ffff3b034cd in msync () at ../sysdeps/unix/syscall-template.S:82 #1

I've been working on adding code coverage support to my ELLCC project (http://ellcc.org) and I thought it would be nice to fun the index page of the HTML output of llvm-cov into something a little prettier and more useful. The initial result is here: http://ellcc.org/coverage/ If there is any interest, I'll submit the llvm-cov changes. -Rich

Le 06/05/2015 21:05, Renato Golin a écrit : > On 6 May 2015 at 19:15, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: >> I could not easily locate this on http://llvm.org/reports/coverage/ so >> asking here: what workload is the coverage computed over? IOW, what >> all does the bot run to get this coverage information? > Nothing is clear in that page. No

I’m working to implement Source Based Code Coverage in a workflow that uses lcov for report generation. We’ve customized our llvm-cov to add a command to convert the SBCC counter data to lcov’s ‘.info’ format. The problem is that the region-based counter definitions in SBCC can span source code regions that can contain blank lines (or lines with only comments). Converting this to lcov’s

Hello guys, Today I tried to find the amount of LLD(elf) code covered by our test cases. So my aim was to run the LLD tests we have (run check-lld task) and find out which code was executed/covered and which was not. I used the approach from the next article to do that: http://logan.tw/posts/2015/04/28/check-code-coverage-with-clang-and-lcov/#create-a-wrapper-script-for-lcov In short, it is

Hi All. I would like to compute a separate covariance matrix for a set of variables for each of the levels of a factor and then compute the average covariance matrix over the factor levels. I can loop through this computation but I need to perform the calculation for a large number of levels and am looking for something more elegant. To be concrete.... u <- 3 n <- 10 x <-

Dear R users: I have a problem about catch the value from function. I have following two functions (part): fbolus1 <- function() {......... par<-data.frame(Parameter=c("kel","Vd"),Initial=c(0)) check(par) .....} check<-function(par) { if (par[ ,2] <= 0){ cat("\nEnter again (y/n) ?\n\n") ans<-readline() if (ans == "n" ){