Displaying 20 results from an estimated 9000 matches similar to: "Which code coverage approach is suggested from LLVM"
2014 Feb 13
2
[LLVMdev] asan coverage
On Feb 12, 2014, at 11:43 PM, Kostya Serebryany <kcc at google.com> wrote:
>
>
>
> On Thu, Feb 13, 2014 at 11:10 AM, Bob Wilson <bob.wilson at apple.com> wrote:
>
> On Feb 12, 2014, at 10:31 AM, Kostya Serebryany <kcc at google.com> wrote:
>
>> Hi,
>>
>> Justin is making nice commits for llvm-cov, so I thought we may continue this
2017 Oct 26
2
[PATCH for-next 0/9] LLVM coverage support for Xen
Hello,
The following patch series enables LLVM coverage support for the Xen
hypervisor. This first patches are a re-organization of the gcov
support, in order to make the support generic for all coverage
technologies. This is mostly a name change from gcov -> cov in several
places and files, together with the addition of a Kconfig option in
order to enable LLVM coverage.
Patch 7 introduces
2015 May 27
0
[LLVMdev] GCC compatibility code coverage issue .
Umesh Kalappa <umesh.kalappa0 at gmail.com> writes:
> Hi Justin ,
>
> Thank you for the confirmation and we would like to know that ,going
> forward the clang has the support the gcc gcov format or use the
> -fprofile-instr-generate -fcoverage-mapping and get ride of gcov
> format .
Going forward, the -fprofile-instr-generate -fcoverage-mapping (which
I'll refer to as
2015 May 22
2
[LLVMdev] GCC compatibility code coverage issue .
Hi Justin ,
Thank you for the confirmation and we would like to know that ,going
forward the clang has the support the gcc gcov format or use the
-fprofile-instr-generate -fcoverage-mapping and get ride of gcov
format .
We are planing to customize the clang code coverage for embedded world
,before we start tweaking the gcov / -fprofile-instr-generate
code-base ,we would like to take feedback
2014 Feb 13
2
[LLVMdev] asan coverage
On Feb 12, 2014, at 10:31 AM, Kostya Serebryany <kcc at google.com> wrote:
> Hi,
>
> Justin is making nice commits for llvm-cov, so I thought we may continue this discussion now.
> The quick-and-dirty implementation of coverage (in asan) is getting some early users and they seem to be happy.
> AsanCoverage allows to collect per-function or per-basic-block coverage
2020 May 04
2
[EXTERNAL] How to get branch coverage by using 'source-based code coverage'
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 =
2020 May 03
2
[EXTERNAL] How to get branch coverage by using 'source-based code coverage'
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
2020 Apr 26
2
How to get branch coverage by using 'source-based code coverage'
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
2016 Mar 13
2
Unable to generate lcov test coverage reports (Out of memory error)
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
2008 May 27
0
[LLVMdev] DejaGnu test-suite coverage
On Mon, May 26, 2008 at 11:27 PM, Gabor Greif <gabor at mac.com> wrote:
> Heh,
>
> my ex-boss would die seeing something like this :-)
It's not too hard to produce, let me know if you want details, or ping me on
IRC.
> Just one comment, does GCOV have a flag for
> a third category of lines, like "undesired to execute"?
Nope. I'm a subscriber to the
2016 Apr 06
2
Writing a test for gcov style coverage crashing after dlclose
Hi Everyone,
I have uploaded a patch that allows one to successfully gather gcov/gcda
coverage information on programs which unload shared libraries. It¹s a
simple fix, just adding a few COMPILER_RT_VISIBILITY (i.e.
__attribute__((visibility("hidden")))) in GCDAProfiling.c.
Now, I¹d like to include a test program to demonstrate the fix. AFAICT,
there seems to be a single test for
2020 Jun 28
3
Introducing the binary-level coverage analysis tool bcov
Hi Fangrui,
Many thanks for providing such detailed feedback! Please find my comments
inlined below.
- Ammar
On Sun, Jun 28, 2020 at 5:59 AM Fangrui Song <maskray at google.com> wrote:
> On 2020-06-26, Ammar Ben Khadra via llvm-dev wrote:
> >## TL;DR
> >
> >We introduce bcov, an open-source binary-level coverage analysis tool [1].
> >The details are discussed
2013 Oct 04
0
[LLVMdev] question about -coverage
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
2008 May 27
2
[LLVMdev] DejaGnu test-suite coverage
Heh,
my ex-boss would die seeing something like this :-)
Just one comment, does GCOV have a flag for
a third category of lines, like "undesired to execute"?
This would make the summary of
<http://chandlerc.net/llvm-coverage/lib/Target/PowerPC/
PPCHazardRecognizers.cpp.gcov.html>
much more favorable.
Nice work!
Cheers,
Gabor
2013 Feb 06
2
[LLVMdev] LLVM Coverage GCDA Flush API
The way `-ftest-coverage -fprofile-arcs` works at the moment it only
flushes via `atexit()`. This patch allows you to flush the coverage at any
point by calling `__llvm_gcov_flush` the same way `__gcov_flush` works for
gcc.
If there is another way of doing this, I might of missed it but I was
looking for `__gcov_flush` and I did not find the equivalent in llvm at the
moment.
--
John Harrison
2013 Feb 06
0
[LLVMdev] LLVM Coverage GCDA Flush API
We do have a gcov "flush" implementation. It should be emitted with the normal coverage code. Is it not showing up?
-bw
On Feb 5, 2013, at 4:20 PM, John Harrison <ash.gti at gmail.com> wrote:
> Hi,
>
> I ran into the bug/feature request that you cannot flush gcov buffers while the app is running. They are only called when you exit the program, since the flush functions
2017 Jun 14
3
LLVM coverage report
Hi Sylvestre,
it seems the code coverage runs are not updated since a couple of
months.
http://llvm.org/reports/coverage/tools/polly/lib/Support/SCEVValidator.cpp.gcov.html
The last run was on 2017-05-20 02:07:48.
Are you still maintaining these? Is this on purpose? Any chance this
could be fixed?
Best,
Tobias
2015 Apr 28
4
[LLVMdev] GCC compatibility code coverage issue .
Hi All,
We trying to use clang+llvm to generate the gcc coverage format as
clang version 3.6.0
$clang --coverage -Xclang -coverage-cfg-checksum -Xclang
-coverage-no-function-names-in-data -Xclang -coverage-version='407*'
test.c
$a.out
$llvm-cov gcov test.gcda
Unexpected version: *704.
Invalid .gcno File!
Debugging the above cause ,But any hints from experts here ,will help a lot
2016 Mar 03
2
[LLVMDev] llvm-cov outputting coverage results as HTML reports
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
2017 Aug 31
0
Re: The issue about code coverage for libguestfs
On Thu, Aug 31, 2017 at 05:45:38AM -0400, Yongkui Guo wrote:
> Hi,
>
> I tried to do code coverage testing for libguestfs with gcov.
>
> The steps are shown as follows:
> 1. Download and install the source package(libguestfs-1.36.5-1.el7.src.rpm)
Probably best to try building this from git instead of using RPMs, so
we can get the changes working upstream first. Make sure to