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 06:18:25 +0000 [thread overview]
Message-ID: <bug-100751-4-SyAeukn3ij@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 #18 from Gejoe <gejoed at rediffmail dot com> ---
(In reply to Martin Liška from comment #14)
> (In reply to Gejoe from comment #13)
> > I modified my sample-prog.c file just by adding a line of __gcov_reset
> > before the while loop.
> >
>
> Can you please create a test-case that does not need human interaction
> (remove getchar please)? Thanks.
I have attached the .c file as attachment 50881 in Comment #16.
I have shown the steps and .gcov file output there as well.
The preprocess file is attached as #50882.
I read your reply in Comment#15 as well.
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.
Thank you for the support !
next prev parent reply other threads:[~2021-05-28 6:18 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 [this message]
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-SyAeukn3ij@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).