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/114751] .gcda:stamp mismatch with notes file
Date: Wed, 24 Apr 2024 11:35:52 +0000 [thread overview]
Message-ID: <bug-114751-4-6K9Wkopvew@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114751-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114751
--- Comment #7 from Gejoe <gejoed at rediffmail dot com> ---
(In reply to Richard Biener from comment #6)
> I have no idea why the values differ but I suspect the copying since we seem
> to use the file modification time at some point. As a workaround I would
> suggest
> to binary-patch one of the file to make the stamp match the other ...
We do use __gcov_dump() in the program execution to get all the gcda files, tar
them up to a file name and we move that to the workspace where build was done
we use a script to run gcov so that gcov files are created finally. So, will
there be any changes in GCC 11.x (compared to 10.3.0) where __gcov_dump and the
ensuing copy process need to be taken care in a better way ?
I'm not sure of the binary-patching of the file mentioned above. Can you
elaborate that suggestion ?
Thank you for bearing with my queries patiently and for the possible help
given.
next prev parent reply other threads:[~2024-04-24 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 7:39 [Bug gcov-profile/114751] New: " gejoed at rediffmail dot com
2024-04-17 8:58 ` [Bug gcov-profile/114751] " rguenth at gcc dot gnu.org
2024-04-17 9:47 ` gejoed at rediffmail dot com
2024-04-18 5:05 ` gejoed at rediffmail dot com
2024-04-23 8:26 ` pinskia at gcc dot gnu.org
2024-04-23 10:47 ` gejoed at rediffmail dot com
2024-04-24 5:03 ` rguenth at gcc dot gnu.org
2024-04-24 11:35 ` gejoed at rediffmail dot com [this message]
2024-04-25 6:24 ` rguenth at gcc dot gnu.org
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-114751-4-6K9Wkopvew@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).