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: David Malcolm <dmalcolm at redhat dot com>, Richard Biener <richard dot guenther at gmail dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Jan Hubicka <hubicka at ucw dot cz>
- Date: Tue, 30 May 2017 08:21:05 +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>
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
>>> eventually rsync
>>> content to a public website:
>>> I guess it can be interesting for instance to see which folding
>>> branches are
>>> not used, or which files (functionality) is basically not much
>>> tested via
>>> the testsuite.
>>> P.S. I've noticed David fixed doxygen of the project, I can rsync
>>> also that
>>> to public website.
>> Nice! Results look better than anticipated ;)
> Excellent; thanks.
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
> extra work?
Yep, it's currently done for gcc subfolder. Can be done in the future.