llvm dev - Aug 2017 - LLVM development trunk - code coverage - branch coverage missing

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 currently branch coverage  metric is not available

Thanks,
Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170823/de60f55b/attachment.html>

On 8/23/2017 10:45 AM, Ravi David via llvm-dev wrote:
>
> 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 .
>
>
http://llvm.org/reports/coverage/ is generated using lcov (on top of 
LLVM's gcov emulation, I think?).  lcov has support for something it 
calls "branch coverage", but it's buggy; when I tried to generate
a
report with it enabled, it hung.

http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html is 
generated using LLVM source-based code coverage 
(https://clang.llvm.org/docs/SourceBasedCodeCoverage.html). Currently, 
it doesn't have any support for decision coverage.

-Eli

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170824/94ac15d5/attachment.html>

Hi Eli , Vedant ,
>> lcov has support for something it calls "branch coverage",
but it's buggy; when I tried to generate a report with it enabled, it hung.
Thanks for your reply.

Even I observed the same behavior with Lcov.

Vedant pointed out that "region coverage metric in the coverage
summary"  will have some info related to branch coverage.

I am planning to explore it , I will get back with details.

--Ravi


From: Friedman, Eli [mailto:efriedma at codeaurora.org]
Sent: Thursday, August 24, 2017 12:53 PM
To: Ravi David <ravid at cadence.com>; llvm-dev at lists.llvm.org
Cc: Vedant Kumar <vsk at apple.com>
Subject: Re: [llvm-dev] LLVM development trunk - code coverage - branch coverage
missing

EXTERNAL MAIL
On 8/23/2017 10:45 AM, Ravi David via llvm-dev wrote:
Hi ,

I could see the LLVM code coverage  info at the below links

http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__lab.llvm.org-3A8080_coverage_coverage-2Dreports_clang_index.html&d=DwMD-g&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=w9rElxRZGeoeI21evGmBSS161LhkODfIGd4A80DWDwg&m=RA6NGBJp_7Wnt4YDyFQ14ECnCDnI9U48TEoZa5JdTWY&s=F68Ai9A6BaLmq5nLqFueBvo3fUZbUAlcUN7KM5nRFoY&e=>
http://llvm.org/reports/coverage/<https://urldefense.proofpoint.com/v2/url?u=http-3A__llvm.org_reports_coverage_&d=DwMD-g&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=w9rElxRZGeoeI21evGmBSS161LhkODfIGd4A80DWDwg&m=RA6NGBJp_7Wnt4YDyFQ14ECnCDnI9U48TEoZa5JdTWY&s=Uc_zrubiOOQikDlJjbvEkeV510qf7OG2LukJKDkfxIg&e=>

I am interested in the branch coverage metric.  I could not find the branch
coverage related info .


http://llvm.org/reports/coverage/<https://urldefense.proofpoint.com/v2/url?u=http-3A__llvm.org_reports_coverage_&d=DwMD-g&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=w9rElxRZGeoeI21evGmBSS161LhkODfIGd4A80DWDwg&m=RA6NGBJp_7Wnt4YDyFQ14ECnCDnI9U48TEoZa5JdTWY&s=Uc_zrubiOOQikDlJjbvEkeV510qf7OG2LukJKDkfxIg&e=>
is generated using lcov (on top of LLVM's gcov emulation, I think?).  lcov
has support for something it calls "branch coverage", but it's
buggy; when I tried to generate a report with it enabled, it hung.

http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__lab.llvm.org-3A8080_coverage_coverage-2Dreports_clang_index.html&d=DwMD-g&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=w9rElxRZGeoeI21evGmBSS161LhkODfIGd4A80DWDwg&m=RA6NGBJp_7Wnt4YDyFQ14ECnCDnI9U48TEoZa5JdTWY&s=F68Ai9A6BaLmq5nLqFueBvo3fUZbUAlcUN7KM5nRFoY&e=>
is generated using LLVM source-based code coverage
(https://clang.llvm.org/docs/SourceBasedCodeCoverage.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__clang.llvm.org_docs_SourceBasedCodeCoverage.html&d=DwMD-g&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=w9rElxRZGeoeI21evGmBSS161LhkODfIGd4A80DWDwg&m=RA6NGBJp_7Wnt4YDyFQ14ECnCDnI9U48TEoZa5JdTWY&s=rH8lu7sallfzpVngYduSm-LRr5oWE4nLpN-eLKkJXWA&e=>).
Currently, it doesn't have any support for decision coverage.

-Eli


--

Employee of Qualcomm Innovation Center, Inc.

Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170824/9ac71f5d/attachment.html>