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: Wed, 13 May 2020 13:38:04 +0000 [thread overview]
Message-ID: <bug-94928-4-I9bXwNlLSv@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 #23 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Myron Walker from comment #22)
> It does the same things a gcov and lcov combined but in python. It also
> does merging of data but in a different way than gcov-tool. I might need to
> change that.
Yes, please use gcov-tool for the merging.
> Another part of it is to allow access to different types of
> resource location hinting. so a gcov prefix for a source code might be a
> github url and token. A gcno file hint might be a web url or sub or nfs
> share. Like wise the data file hints might be http, smb or nfs prefixes.
That should be done by your script. I realized that for the JSON format you
only need to put together .gcda and .gcno files:
$ ls
tramp3d-v4.gcda tramp3d-v4.gcno
$ gcov tramp3d-v4.gcda -i
...
$ gunzip tramp3d-v4.gcda.gcov.json.gz
$ cat tramp3d-v4.gcda.gcov.json | python -m json.tool | grep '"file"'
"file": "tramp3d-v4.cpp",
"file": "/usr/include/c++/6/ext/new_allocator.h",
"file": "/usr/include/c++/6/ext/aligned_buffer.h",
"file": "/usr/include/c++/6/bits/move.h",
"file": "/usr/include/c++/6/bits/alloc_traits.h",
"file": "/usr/include/c++/6/bits/stl_list.h",
"file": "/usr/include/c++/6/bits/allocator.h",
"file": "/usr/include/c++/6/bits/allocated_ptr.h",
"file": "/usr/include/c++/6/bits/stl_iterator.h",
"file": "/usr/include/c++/6/bits/list.tcc",
"file": "/usr/include/c++/6/bits/stl_vector.h",
"file": "/usr/include/c++/6/iostream",
"file": "/usr/include/c++/6/bits/stl_construct.h",
"file": "/usr/include/c++/6/bits/stl_uninitialized.h",
"file": "/usr/include/c++/6/bits/vector.tcc",
"file": "/usr/include/c++/6/bits/stl_algobase.h",
"file": "/usr/include/c++/6/bits/stl_pair.h",
"file": "/usr/include/c++/6/bits/cpp_type_traits.h",
"file": "/usr/include/c++/6/bits/stl_bvector.h",
"file": "/usr/include/c++/6/ext/alloc_traits.h",
"file": "/usr/include/c++/6/bits/predefined_ops.h",
"file": "/usr/include/c++/6/bits/stl_heap.h",
"file": "/usr/include/c++/6/bits/stl_iterator_base_funcs.h",
"file": "/usr/include/c++/6/bits/stl_iterator_base_types.h",
"file": "/usr/include/c++/6/bits/stl_tree.h",
"file": "/usr/include/c++/6/bits/stl_algo.h",
"file": "/usr/include/c++/6/ext/type_traits.h",
"file": "/usr/include/c++/6/bits/stl_function.h",
"file": "/usr/include/c++/6/bits/basic_string.tcc",
"file": "/usr/include/c++/6/bits/basic_string.h",
"file": "/usr/include/c++/6/bits/stl_map.h",
"file": "/usr/include/c++/6/iomanip",
"file": "/usr/include/c++/6/limits",
"file": "/usr/include/c++/6/new",
"file": "/usr/include/c++/6/bits/char_traits.h",
"file": "/usr/include/c++/6/cmath",
And now your script can find and get the corresponding source files.
>
> https://github.com/myronww/pycover
>
> Still a work in progress though.
prev parent reply other threads:[~2020-05-13 13:38 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
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 [this message]
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-I9bXwNlLSv@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).