Hi all! 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: https://gist.github.com/miyuki-chan/943efe7d8e0eb72fdd74997c8a10d6c5 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) I hope, you might find some of these ideas helpful. On Tue, May 30, 2017 at 9:21 AM, Martin Liška <mli...@suse.cz> 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 <mli...@suse.cz> >>> wrote: >>>> Hello. >>>> >>>> I've been working on some patches for GCOV and lcov was of my test >>>> scenarios. >>>> I'm sending link to static HTML pages made by the tool which are >>>> recorded >>>> for GCC (w/o bootstrap) build + running test-suite on x86_64-linux >>>> -gnu. >>>> 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. >>>> >>>> https://drive.google.com/open?id=0B0pisUJ80pO1X0s3eEpuQ25GTG8 >>>> >>>> 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 ;) >>> >>> Richard. >>> >>>> Martin >> >> Excellent; thanks. > > Hello. > > I've just done that, periodically built LCOV can be found here: > > http://gcc.opensuse.org/gcc-lcov/ > >> >> 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. > > Martin > >> >> Dave >> > -- Regards, Mikhail Maltsev
