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: Tue, 23 Apr 2024 10:47:32 +0000 [thread overview]
Message-ID: <bug-114751-4-SuuS04GAWD@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 #5 from Gejoe <gejoed at rediffmail dot com> ---
(In reply to Gejoe from comment #2)
> For me, it is like this (just keeping the sample filenames as such but the
> values are real ones shown while checking with gcov-dump) :
>
> $gcov-dump ./obj-dir-path/src-file.gcda
> ./obj-dir-path/src-file.gcda:data:magic `gcda':version `B14*'
> ./obj-dir-path/src-file.gcda:stamp 2912455990
> :
> <the rest truncated>
>
> $ gcov-dump ./obj-dir-path/src-file.gcno
> ./obj-dir-path/src-file.gcno:note:magic `gcno':version `B14*'
> ./obj-dir-path/src-file.gcno:stamp 2912494680
> :
> <the rest truncated>
>
> Does this indicate something more to be checked ?
>
> In the previous branch where gcc 10.3.0 is used, I could see same stamp
> value for the gcov-dump of same gcda and gcno files there - 3176078538.
>
> Awaiting reply.
>
> Thanks.
Hi team,
Can I expect any reply on my message posted above ?
Thanks,
Gejoe
next prev parent reply other threads:[~2024-04-23 10:47 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 [this message]
2024-04-24 5:03 ` rguenth at gcc dot gnu.org
2024-04-24 11:35 ` gejoed at rediffmail dot com
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-SuuS04GAWD@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).