https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #23 from Martin Liška ---
(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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #22 from Myron Walker ---
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. Another part of it is to allow access to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #21 from Martin Liška ---
(In reply to Myron Walker from comment #20)
> So I will probably continue working on the python script or package that can
> do much of the enhanced processing. One of the benefits of the python is I
> can
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #20 from Myron Walker ---
So I will probably continue working on the python script or package that can do
much of the enhanced processing. One of the benefits of the python is I can
process the code coverage data outside of a build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
Martin Liška changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #18 from CVS Commits ---
The master branch has been updated by Martin Liska :
https://gcc.gnu.org/g:10a9bf806cf180915c20f9971d33da8ff2d663c1
commit r11-260-g10a9bf806cf180915c20f9971d33da8ff2d663c1
Author: Martin Liska
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #17 from Martin Liška ---
All right, I'll prepare a patch for that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #16 from Myron Walker ---
Just seems easier if the tool offers a choice.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #15 from Martin Liška ---
(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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #14 from Myron Walker ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #13 from Martin Liška ---
(In reply to Myron Walker from comment #12)
> What would be helpful then is if gcno, gcda and source files could all have
> separate root file system prefixes.
Can you please describe more the situation?
Is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #12 from Myron Walker ---
What would be helpful then is if gcno, gcda and source files could all have
separate root file system prefixes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #11 from Myron Walker ---
Ok. I'll look into it
On Wed, May 6, 2020, 7:25 AM marxin at gcc dot gnu.org <
gcc-bugzi...@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
>
> --- Comment #10 from Martin Liška
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #10 from Martin Liška ---
(In reply to Myron Walker from comment #9)
> How you I process data files from multiple sources and multiple runs with
> gcov.
$ man gcov-tool
$ gcov-tool merge [merge-options] directory1 directory2
So
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #9 from Myron Walker ---
How you I process data files from multiple sources and multiple runs with gcov.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #8 from Martin Liška ---
Or even better: you can merge various .gcda files with:
gcov-tool merge ...
https://gcc.gnu.org/onlinedocs/gcc/Gcov-tool-Intro.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #7 from Martin Liška ---
(In reply to Myron Walker from comment #6)
> I use the gcno file to build a the graph, pull counters from the gcda files
> and then solve the graph for the missing counts.
That's what gcov does itself.
> I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #6 from Myron Walker ---
I use the gcno file to build a the graph, pull counters from the gcda files and
then solve the graph for the missing counts. I am merging the data from
multiple gcda sources. Multiple nodes running the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #5 from Martin Liška ---
(In reply to Myron Walker from comment #4)
> A python tool that can do distributed code coverage analysis. Gcda files
> from cluster nodes from a web interface, gcno from a web interface or file
> share in a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #4 from Myron Walker ---
A python tool that can do distributed code coverage analysis. Gcda files from
cluster nodes from a web interface, gcno from a web interface or file share in
a build archive, and source directly from github.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #3 from Martin Liška ---
(In reply to Myron Walker from comment #2)
> I am parsinv both gcno and gcda files.
These files are not intended to be parsed :/
Can you please describe your use-case?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #2 from Myron Walker ---
I am parsinv both gcno and gcda files.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
--- Comment #1 from Martin Liška ---
You are right, the documentation is not complete.
Btw. are you parsing a .gcda or .gcna format for some reason?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928
Martin Liška changed:
What|Removed |Added
Target Milestone|--- |11.0
Ever confirmed|0
24 matches
Mail list logo
