This is the mail archive of the
mailing list for the GCC project.
Re: LCOV of current GCC
- From: Martin Liška <mliska at suse dot cz>
- To: Mikhail Maltsev <maltsevm at gmail dot com>
- Cc: David Malcolm <dmalcolm at redhat dot com>, Richard Biener <richard dot guenther at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>, Jan Hubicka <hubicka at ucw dot cz>
- Date: Tue, 11 Jul 2017 15:21:20 +0200
- Subject: Re: LCOV of current GCC
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org> <CAFiYyc0JgssAsC-7FOyhhPHKj70cQfrXxb+Vzdi=t+-oeUTe4A@mail.gmail.com> <email@example.com> <firstname.lastname@example.org> <CAOqAUTidf1PcCE3zwZC98UHwHu_frsABmWov-2sm6ow=Ob4hOA@mail.gmail.com>
On 07/02/2017 07:19 PM, Mikhail Maltsev wrote:
I noticed that you started to publish GCC test coverage data. About a
year ago I also experimented with GCC's coverage and would like to
share some possible improvement ideas for your scripts.
I postprocess the coverage data with this script:
Thank you for the notes. As my build is driven by buildbot I decided to incorporate
It has the following features:
1. removes gengtype routines from coverage data
2. removes code from system headers (e.g., the host libstdc++)
3. it outputs a summary (which can be used for building graphs, like
you do for benchmarks)
Yep, written to my TODO list.
Please be aware that we have some connection issues with gcc.opensuse.org, but
updated LCOV will appear there soon.
I hope, you might find some of these ideas helpful.
On Tue, May 30, 2017 at 9:21 AM, Martin Liška <email@example.com> wrote:
On 04/28/2017 06:53 PM, David Malcolm wrote:
On Fri, 2017-04-28 at 11:38 +0200, Richard Biener wrote:
On Fri, Apr 28, 2017 at 11:07 AM, Martin Liška <firstname.lastname@example.org>
I've been working on some patches for GCOV and lcov was of my test
I'm sending link to static HTML pages made by the tool which are
for GCC (w/o bootstrap) build + running test-suite on x86_64-linux
I'm planning to set up a periodic build of that that will
content to a public website:
I guess it can be interesting for instance to see which folding
not used, or which files (functionality) is basically not much
P.S. I've noticed David fixed doxygen of the project, I can rsync
to public website.
Nice! Results look better than anticipated ;)
I've just done that, periodically built LCOV can be found here:
For your periodic builds, please can you add "jit" to the enabled
languages (it will also need --enable-host-shared).
Done that and will be seen in next build. I do it every weekend.
Would be nice to add libiberty and libcpp to this, but maybe that needs
Yep, it's currently done for gcc subfolder. Can be done in the future.