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/97923] [GCOV]Wrong code coverage for multiple expressions with Logical OR Operator at multiple lines
Date: Thu, 08 Sep 2022 09:42:29 +0000	[thread overview]
Message-ID: <bug-97923-4-ptKy6IqYzI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97923-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97923

--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Really, I see still the same:

$ gcc --version
gcc (GCC) 13.0.0 20220908 (experimental)
$ gcc -O0 --coverage test.c; ./a.out; gcov a-test.c; cat test.c.gcov
File 'test.c'
Lines executed:80.00% of 5
Creating 'test.c.gcov'

Lines executed:80.00% of 5
        -:    0:Source:test.c
        -:    0:Graph:a-test.gcno
        -:    0:Data:a-test.gcda
        -:    0:Runs:1
        1:    1:int foo(int c)
        -:    2:{
    #####:    3:  return ((c >= 'A' && c <= 'Z')
       1*:    4:       || (c >= 'a' && c <= 'z')
       2*:    5:       || (c >= '0' && c <= '0'));
        -:    6:}
        -:    7:
        1:    8:int main() { foo(0); }

  parent reply	other threads:[~2022-09-08  9:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20  2:41 [Bug gcov-profile/97923] New: " yangyibiao at outlook dot com
2020-11-20  9:35 ` [Bug gcov-profile/97923] " marxin at gcc dot gnu.org
2022-09-08  7:49 ` yangyibiao at nju dot edu.cn
2022-09-08  9:42 ` marxin at gcc dot gnu.org [this message]
2022-09-08 11:13 ` yangyibiao at nju dot edu.cn
2023-03-01  2:07 ` yinyuefengyi at gmail dot com
2023-03-01  2:10 ` yinyuefengyi at gmail dot com

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-97923-4-ptKy6IqYzI@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).