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 05:49:15 +0000 [thread overview] Message-ID: <bug-100751-4-3MLqfq1qFE@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 #16 from Gejoe <gejoed at rediffmail dot com> --- Created attachment 50881 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50881&action=edit sample-prog.c edited to show __gcov_reset call. The steps used for compiling and running the attached .c file are as follows: gcc -v -save-temps -fprofile-arcs -ftest-coverage sample-prog.c gcc -fprofile-arcs -ftest-coverage sample-prog.o ./a.out The output of a.out run is : __gcov_dump() invoked! __gcov_reset() invoked! __gcov_dump() invoked! __gcov_reset() invoked! $ gcov sample-prog.c sample-prog.c:source file is newer than notes file 'sample-prog.gcno' (the message is displayed only once per source file) File 'sample-prog.c' Lines executed:83.33% of 18 Creating 'sample-prog.c.gcov' $ cat sample-prog.c.gcov -: 0:Source:sample-prog.c -: 0:Graph:sample-prog.gcno -: 0:Data:sample-prog.gcda -: 0:Runs:2 -: 0:Programs:1 -: 0:Source is newer than graph -: 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: 2: 9:int main() -: 10:{ -: 11: unsigned char c; 2: 12: int count=0; 2: 13: c = 'g'; -: 14: -: 15: do { -: 16: -: 17: if(c == 'g'){ -: 18: __gcov_dump(); 20: 19: printf("__gcov_dump() invoked!\n"); 4: 20: c = 'r'; #####: 21: } #####: 22: else if(c == 'r'){ -: 23: __gcov_reset(); 16: 24: printf("__gcov_reset() invoked!\n"); #####: 25: c = 'f'; 4: 26: } 4: 27: if(count == 2) -: 28: c = 'g'; 20: 29: else if (count > 10) 2: 30: c = 'e'; 18: 31: count++; 2: 32: }while(c != 'e'); 20: 33: 20: 34: return 0; -: 35:}
next prev parent reply other threads:[~2021-05-28 5:49 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 [this message] 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 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-3MLqfq1qFE@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: linkBe 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).