similar to: Customizing SBCC for lcov workflows

Hey Guys ! I'm interested to participate in Google Summer of Code 2018 for LLVM. Any Projects (new features or reimplementation) related to recent " Meltdown & Spectre " Problem. I'm a beginner in Compiler Technology. Could you please recommend some videos or blog post about "*Introduction to LLVM internals ". *Because I find it difficult to understand LLVM IR

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

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

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

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 =

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? -- Sanjoy On Wed, May 6, 2015 at 10:17 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Wed, May 6, 2015 at 8:28 AM, Renato Golin <renato.golin at linaro.org> > wrote:

Folks, I was looking at LCOV (http://llvm.org/reports/coverage/) and it's nice and all, but it doesn't have much information about which commit is that and the difference between two commits. We could then have a that report for every buildbot (check-all, test-suite, etc) for the patches specific to the build, per architecture. How easy would be to do that for any given buildbot? Another

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

Dear All, I am helping our test team migrate from gcov to llvmcov. They currently generate HTML reports using lcov to easily navigate where coverage is missing. However, there does not seem to be a Windows compatible solution for generating HTML reports using the llvm-cov tools. A possible solution to this problem is for llvm-cov to create html pages that include an overall coverage summary

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

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 <-

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

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

Thanks a lot for doing this. Having it automated an in a bot would be really nice. Cheers, Rafael George Rimar <grimar at accesssoftek.com> writes: > 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. > >

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

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

Hi We're a group of 5 CS undergrads. As a part of our Software Engineering course, we are required to work on a large scale software to understand the design of such software. For this, open source is the best choice. We have around 1.5 months for the project (mid-March to April end) and would like to know whether there is any sort of work which can be taken up by us. Looking forward to your

The PGO was my first guess but I can get a lot of information. At first, I follow the explanation at http://clang.llvm.org/docs/UsersManual.html#profiling-with-instrumentation but instead of llvm-profdata merge, I used llvm-profdata show *.profraw. Sadly, the information I get is the total number of function, the maximum function count and the maximum internal block count. Do you know if you

Hi, Is there something wrong with lcov.xapian.org ? It seems my quassel client suddenly can't connect to it. ------------------ Shangtong Zhang,Second Year Undergraduate, School of Computer Science, Fudan University, China. -------------- next part -------------- An HTML attachment was scrubbed... URL: