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: Thu, 19 Aug 2021 21:20:24 +0000 [thread overview]
Message-ID: <bug-89961-4-WbfXzvNe5s@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
--- Comment #23 from xaizek <xaizek at posteo dot net> ---
> it should be fixed in the updated version of the patch.
Yes, it is.
> Right now, one can easily detect JSON format with
> `gcov --help | grep json-format`, am I right? What type of capability would
> you appreciate?
Correct, but `--help` and `--version` are formatted for humans, not machines.
This can lead to false positives or negatives. It forces every application
that
calls gcov and wants to support wide range of versions to embed its copy of
knowledge about gcov's development history. And `--help` won't tell if `-x`
works with `--json-format`, that's why `--version` needs to be used as well.
For consistency, since there is output for machines, it would be nice to have a
way to know how to get it and what to expect from it for machines as well.
I'd include any addition/removal/change between versions that makes difference,
like "has-json-format-option", "can-hash-json-files", "has-stdout-option".
Basically a hard-coded list that's easy to check.
This isn't so much for existing releases (unless it's backported), but in
anticipation of future changes that can affect the caller. I don't have an
example of such interface in apps, just wanted to bring it up for your
consideration.
next prev parent reply other threads:[~2021-08-19 21:20 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
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 [this message]
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-WbfXzvNe5s@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).