public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/106090] [GCOV] Wrong coverage for loop statements
Date: Mon, 04 Jul 2022 11:36:41 +0000 [thread overview]
Message-ID: <bug-106090-4-oR6GPbCbeT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106090-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106090
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
> do_it() is indeed called 4 times,but I wonder how the coverage statistiscs
> of the for-statement is calculated. It doesn't become 5 untill the
> for-stamentment is completed.
We count a line every time there exists a jump from a different line that jumps
to the line.
Thus for `for(;;)` there are no statements we should jump to.
next prev parent reply other threads:[~2022-07-04 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:06 [Bug gcov-profile/106090] New: " njuwy at smail dot nju.edu.cn
2022-06-27 13:45 ` [Bug gcov-profile/106090] " marxin at gcc dot gnu.org
2022-07-03 3:19 ` njuwy at smail dot nju.edu.cn
2022-07-03 3:23 ` njuwy at smail dot nju.edu.cn
2022-07-04 11:36 ` marxin at gcc dot gnu.org [this message]
2022-07-04 12:15 ` njuwy at smail dot nju.edu.cn
2022-07-04 13:05 ` njuwy at smail dot nju.edu.cn
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=bug-106090-4-oR6GPbCbeT@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).