public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/94928] Doc comments in gcov-io.h do not show cwd and unexec blocks in the Notes file format
Date: Thu, 07 May 2020 11:17:00 +0000 [thread overview]
Message-ID: <bug-94928-4-4cPRfOLThG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94928-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #15 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Myron Walker from comment #14)
> There are three types of files used to create a code coverage report.
> Notes, Data, and Source. It is likely that each type of file might have its
> own prefix GCOV_SRC_PREFIX, GCOV_NOTES_PREFIX and GCOC_DATA_PREFIX
How difficult would it be to arrange all 3 types together? I mean x.gcda y.gcno
files should be in a same folder. With source files, it's more difficult as
they can be compiled in a prefixed directory, but e.g. system header files are
not prepended with a prefix, right?
The easiest approach seem to me copying .gcda and .gcno files into
corresponding location in source file directory.
next prev parent reply other threads:[~2020-05-07 11:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 22:09 [Bug gcov-profile/94928] New: " myron.walker at gmail dot com
2020-05-04 5:38 ` [Bug gcov-profile/94928] " marxin at gcc dot gnu.org
2020-05-06 9:14 ` marxin at gcc dot gnu.org
2020-05-06 13:13 ` myron.walker at gmail dot com
2020-05-06 13:17 ` marxin at gcc dot gnu.org
2020-05-06 13:31 ` myron.walker at gmail dot com
2020-05-06 13:38 ` marxin at gcc dot gnu.org
2020-05-06 13:52 ` myron.walker at gmail dot com
2020-05-06 13:59 ` marxin at gcc dot gnu.org
2020-05-06 14:04 ` marxin at gcc dot gnu.org
2020-05-06 14:14 ` myron.walker at gmail dot com
2020-05-06 14:21 ` marxin at gcc dot gnu.org
2020-05-06 14:57 ` myron.walker at gmail dot com
2020-05-06 15:22 ` myron.walker at gmail dot com
2020-05-07 7:35 ` marxin at gcc dot gnu.org
2020-05-07 10:41 ` myron.walker at gmail dot com
2020-05-07 11:17 ` marxin at gcc dot gnu.org [this message]
2020-05-07 13:37 ` myron.walker at gmail dot com
2020-05-11 7:22 ` marxin at gcc dot gnu.org
2020-05-11 7:26 ` cvs-commit at gcc dot gnu.org
2020-05-11 8:06 ` marxin at gcc dot gnu.org
2020-05-11 14:45 ` myron.walker at gmail dot com
2020-05-11 18:36 ` marxin at gcc dot gnu.org
2020-05-11 19:05 ` myron.walker at gmail dot com
2020-05-13 13:38 ` 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-94928-4-4cPRfOLThG@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).