public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sara Graovac <Sara.Graovac@syrmia.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: Problem with counting code coverage lines - return statement
Date: Mon, 4 Oct 2021 07:30:22 +0000	[thread overview]
Message-ID: <AM7PR03MB6417FD3BA4A8FD50A1E8D304E8AE9@AM7PR03MB6417.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <AM7PR03MB64179F284E0883E7570534C8E8A19@AM7PR03MB6417.eurprd03.prod.outlook.com>

Hi,

Do you have time to look at this?

Best regards,
Sara Graovac

From: Sara Graovac
Sent: 21 September, 2021 16:15
To: gcc-help@gcc.gnu.org
Subject: Problem with counting code coverage lines - return statement


Hi,

We use your tool gcov, exactly lcov, for code coverage. It is important to us.
We find a problem with counting lines, when in return statement call the
other function and the arguments of the function are on two lines, because of alignment.

Sometimes it counts only first line, sometimes it counts both lines.
In my current project first line is counted 109 times, the second one is counted 14 times.

I send you the example of return statement, please see attachment.

I tried to find where the problem is.
Can you help me to fix it?

Kind regards,
Sara Graovac
Contactor Syrmia
Software Engineer
Virtualization

Office:
Djordja Stanojevica 12
11070 Belgrade, Serbia
Phone: +(381)-21-4831-210
E-mail: sara.graovac@amd.com<mailto:sara.graovac@amd.com>
               sara.graovac@syrmia.com<mailto:sara.graovac@syrmia.com>

Headquarters:
Syrmia LLC @ Belgrade Office Park
Djordja Stanojevica 12,
11070 Belgrade, Serbia
www.syrmia.com<http://www.syrmia.com/>


  reply	other threads:[~2021-10-04  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 14:14 Sara Graovac
2021-10-04  7:30 ` Sara Graovac [this message]
2021-10-04 15:20   ` Dan Kegel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM7PR03MB6417FD3BA4A8FD50A1E8D304E8AE9@AM7PR03MB6417.eurprd03.prod.outlook.com \
    --to=sara.graovac@syrmia.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).