public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gejoed at rediffmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/100751] __gcov_dump and __gcov_reset usage
Date: Fri, 28 May 2021 09:57:40 +0000	[thread overview]
Message-ID: <bug-100751-4-QtRuHpSKuh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100751-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from Gejoe <gejoed at rediffmail dot com> ---
(In reply to Martin Liška from comment #20)
> > I'm trying to understand line #22 to #26 specifically of .c.gcov file(as
> > shown in commment #16. Let me know if the steps followed in compilation or
> > execution had any thing wrong.
> 
> What is wrong with that? What values are expected?

Actually if we look at line #22 should have the value 16 (after a.out run) and
line #24,25 should have values 4 each instead of what is actually present there
in comment#16.Instead the value of 16,4,4 are shown for line # 24,26,27
respectively. That was my query.

Is that because of some difference with source files and .gcda files as shown
there (in .c.gcov file in Comment #16) as follows ? 
    0:Source is newer than graph

I did delete the gcda file and did the same compilation steps again :
$ gcc -v -save-temps  -fprofile-arcs -ftest-coverage sample-prog.c
$ gcc   -fprofile-arcs -ftest-coverage sample-prog.o
$./a.out

The output was :
$ ./a.out 
__gcov_dump() invoked!
__gcov_reset() invoked!
__gcov_dump() invoked!
__gcov_reset() invoked!

The sample-prog.c.gcov file contents now look fine :
        -:    0:Source:sample-prog.c
        -:    0:Graph:sample-prog.gcno
        -:    0:Data:sample-prog.gcda
        -:    0:Runs:1
        -:    0:Programs:1
        -:    1:#include <stdio.h>
        -:    2:#include <ctype.h>
        -:    3:#include <unistd.h>
        -:    4:
        -:    5:extern void __gcov_reset(void);
        -:    6:extern void __gcov_flush(void);
        -:    7:extern void __gcov_dump( void);
        -:    8:
        1:    9:int main()
        -:   10:{
        -:   11:    unsigned char c;
        1:   12:    int count=0;
        1:   13:        c = 'g';
        -:   14:
        -:   15:        do {
        -:   16:   
       10:   17:                if(c == 'g'){
        2:   18:                        __gcov_dump();
    #####:   19:                        printf("__gcov_dump() invoked!\n");
    #####:   20:                        c = 'r';
        -:   21:                }
        8:   22:                else if(c == 'r'){
    #####:   23:                        __gcov_reset();
        2:   24:                        printf("__gcov_reset() invoked!\n");
        2:   25:                        c = 'f';
        -:   26:                }
       10:   27:                if(count == 2)
        1:   28:                        c = 'g';
        9:   29:                else if (count > 10)
        1:   30:                        c = 'e';
       10:   31:                count++;
       10:   32:        }while(c != 'e');
        -:   33:    
        1:   34:        return 0;
        -:   35:}
==========================================================

So, for either a one time call of __gcov_dump (though we may attempt to call
__gcov_dump many times)  or at the exit of the program execution, the merge of
profile happens due to which __gcov_reset doesn't get reflected at all. Am I
right ?

Thanks again!

  parent reply	other threads:[~2021-05-28  9:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  6:54 [Bug gcov-profile/100751] New: " gejoed at rediffmail dot com
2021-05-25  6:58 ` [Bug gcov-profile/100751] " gejoed at rediffmail dot com
2021-05-25  7:01 ` gejoed at rediffmail dot com
2021-05-25  7:56 ` marxin at gcc dot gnu.org
2021-05-25 10:57 ` gejoed at rediffmail dot com
2021-05-25 12:14 ` gejoed at rediffmail dot com
2021-05-25 12:52 ` marxin at gcc dot gnu.org
2021-05-25 12:53 ` marxin at gcc dot gnu.org
2021-05-25 18:40 ` gejoed at rediffmail dot com
2021-05-26  7:31 ` marxin at gcc dot gnu.org
2021-05-26  7:34 ` cvs-commit at gcc dot gnu.org
2021-05-26  7:34 ` marxin at gcc dot gnu.org
2021-05-26 15:13 ` gejoed at rediffmail dot com
2021-05-27 13:53 ` gejoed at rediffmail dot com
2021-05-27 13:57 ` marxin at gcc dot gnu.org
2021-05-27 13:58 ` marxin at gcc dot gnu.org
2021-05-28  5:49 ` gejoed at rediffmail dot com
2021-05-28  6:15 ` gejoed at rediffmail dot com
2021-05-28  6:18 ` gejoed at rediffmail dot com
2021-05-28  6:22 ` gejoed at rediffmail dot com
2021-05-28  7:30 ` marxin at gcc dot gnu.org
2021-05-28  9:57 ` gejoed at rediffmail dot com [this message]
2021-05-28 11:38 ` cvs-commit at gcc dot gnu.org
2021-05-28 11:41 ` marxin at gcc dot gnu.org
2021-06-01  5:25 ` gejoed at rediffmail 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-100751-4-QtRuHpSKuh@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).