public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xaizek at posteo dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/89961] When "--intermediate-format" is used "--preserve-paths"/"--hash-filenames" is ignored
Date: Mon, 31 May 2021 12:28:59 +0000 [thread overview]
Message-ID: <bug-89961-4-rb8vTVKMUH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89961-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961
xaizek <xaizek at posteo dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xaizek at posteo dot net
--- Comment #11 from xaizek <xaizek at posteo dot net> ---
> Closing this as fixed.
This isn't fixed. I don't think the problem was actually understood.
Say you have:
* src/myclass.o
* tests/myclass.o
If you run `gcov -p -x --json-format src/myclass.o` you get
myclass.gcov.json.gz for that file, running `gcov -p -x --json-format
tests/myclass.o` gives you myclass.gcov.json.gz for the test. Running `gcov -p
-x --json-format src/myclass.o tests/myclass.o` gives myclass.gcov.json.gz *FOR
THE TEST ONLY*, because gcov created output for src/myclass.o and then replaced
it.
>From reading your comment I thought that maybe gcov combines information from
two files before writing the result to address this issue, but it doesn't.
Results you get depends on the order in which files are specified.
Either -p and -x need to be obeyed or reports need to be merged. If combining
is implemented, might as well combine all reports and write a single file
specified on command line (--json-format=myfile.gz or --json-format=- (no
compression needed)).
next parent reply other threads:[~2021-05-31 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-89961-4@http.gcc.gnu.org/bugzilla/>
2021-05-31 12:28 ` xaizek at posteo dot net [this message]
2021-05-31 12:48 ` marxin at gcc dot gnu.org
2021-08-16 12:26 ` marxin at gcc dot gnu.org
2021-08-16 17:11 ` xaizek at posteo dot net
2021-08-16 17:16 ` xaizek at posteo dot net
2021-08-17 14:22 ` marxin at gcc dot gnu.org
2021-08-17 14:23 ` marxin at gcc dot gnu.org
2021-08-17 16:52 ` xaizek at posteo dot net
2021-08-18 9:46 ` marxin at gcc dot gnu.org
2021-08-18 20:31 ` xaizek at posteo dot net
2021-08-19 8:56 ` marxin at gcc dot gnu.org
2021-08-19 8:57 ` marxin at gcc dot gnu.org
2021-08-19 21:20 ` xaizek at posteo dot net
2021-08-20 8:06 ` marxin at gcc dot gnu.org
2021-08-20 8:07 ` cvs-commit at gcc dot gnu.org
2021-08-20 8:09 ` marxin at gcc dot gnu.org
2021-08-23 8:55 ` cvs-commit at gcc dot gnu.org
2021-08-23 8:56 ` marxin 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-89961-4-rb8vTVKMUH@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).