* LCOV of current GCC @ 2017-04-28 9:07 Martin Liška 2017-04-28 9:38 ` Richard Biener 0 siblings, 1 reply; 8+ messages in thread From: Martin Liška @ 2017-04-28 9:07 UTC (permalink / raw) To: GCC Development; +Cc: Jan Hubicka, David Malcolm, Richard Biener 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. Martin ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: LCOV of current GCC 2017-04-28 9:07 LCOV of current GCC Martin Liška @ 2017-04-28 9:38 ` Richard Biener 2017-04-28 15:39 ` Jeff Law 2017-04-28 16:53 ` David Malcolm 0 siblings, 2 replies; 8+ messages in thread From: Richard Biener @ 2017-04-28 9:38 UTC (permalink / raw) To: Martin Liška; +Cc: GCC Development, Jan Hubicka, David Malcolm On Fri, Apr 28, 2017 at 11:07 AM, Martin Liška <mliska@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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: LCOV of current GCC 2017-04-28 9:38 ` Richard Biener @ 2017-04-28 15:39 ` Jeff Law 2017-04-28 17:16 ` Joseph Myers 2017-04-28 16:53 ` David Malcolm 1 sibling, 1 reply; 8+ messages in thread From: Jeff Law @ 2017-04-28 15:39 UTC (permalink / raw) To: Richard Biener, Martin Liška Cc: GCC Development, Jan Hubicka, David Malcolm On 04/28/2017 03:38 AM, Richard Biener wrote: > On Fri, Apr 28, 2017 at 11:07 AM, Martin LiÅ¡ka <mliska@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 ;) I did some similar work a few years back. Martin's results are comparable to mine. Interestingly enough the 70-80% coverage we see for GCC is a "sweet spot" in that several of the ancillary tools I tested were in the same overall range. jeff ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: LCOV of current GCC 2017-04-28 15:39 ` Jeff Law @ 2017-04-28 17:16 ` Joseph Myers 0 siblings, 0 replies; 8+ messages in thread From: Joseph Myers @ 2017-04-28 17:16 UTC (permalink / raw) To: Jeff Law Cc: Richard Biener, Martin Liška, GCC Development, Jan Hubicka, David Malcolm On Fri, 28 Apr 2017, Jeff Law wrote: > I did some similar work a few years back. Martin's results are comparable to > mine. Interestingly enough the 70-80% coverage we see for GCC is a "sweet > spot" in that several of the ancillary tools I tested were in the same overall > range. My observation from looking at some of the C front-end results is that many of the coverage omissions are from features only used / supported on certain architectures, e.g. address spaces and fixed point (though actually there are address spaces on x86, but maybe not tests covering much of the generic address space support). -- Joseph S. Myers joseph@codesourcery.com ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: LCOV of current GCC 2017-04-28 9:38 ` Richard Biener 2017-04-28 15:39 ` Jeff Law @ 2017-04-28 16:53 ` David Malcolm 2017-05-30 6:21 ` Martin Liška 1 sibling, 1 reply; 8+ messages in thread From: David Malcolm @ 2017-04-28 16:53 UTC (permalink / raw) To: Richard Biener, Martin Liška; +Cc: GCC Development, Jan Hubicka On Fri, 2017-04-28 at 11:38 +0200, Richard Biener wrote: > On Fri, Apr 28, 2017 at 11:07 AM, Martin LiÅ¡ka <mliska@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. For your periodic builds, please can you add "jit" to the enabled languages (it will also need --enable-host-shared). Would be nice to add libiberty and libcpp to this, but maybe that needs extra work? Dave ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: LCOV of current GCC 2017-04-28 16:53 ` David Malcolm @ 2017-05-30 6:21 ` Martin Liška 2017-07-02 17:19 ` Mikhail Maltsev 0 siblings, 1 reply; 8+ messages in thread From: Martin Liška @ 2017-05-30 6:21 UTC (permalink / raw) To: David Malcolm, Richard Biener; +Cc: GCC Development, Jan Hubicka 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 <mliska@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 > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: LCOV of current GCC 2017-05-30 6:21 ` Martin Liška @ 2017-07-02 17:19 ` Mikhail Maltsev 2017-07-11 13:21 ` Martin Liška 0 siblings, 1 reply; 8+ messages in thread From: Mikhail Maltsev @ 2017-07-02 17:19 UTC (permalink / raw) To: Martin Liška Cc: David Malcolm, Richard Biener, GCC Development, Jan Hubicka 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 <mliska@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 <mliska@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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: LCOV of current GCC 2017-07-02 17:19 ` Mikhail Maltsev @ 2017-07-11 13:21 ` Martin Liška 0 siblings, 0 replies; 8+ messages in thread From: Martin Liška @ 2017-07-11 13:21 UTC (permalink / raw) To: Mikhail Maltsev Cc: David Malcolm, Richard Biener, GCC Development, Jan Hubicka On 07/02/2017 07:19 PM, Mikhail Maltsev wrote: > 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 Hello. Thank you for the notes. As my build is driven by buildbot I decided to incorporate your changes: > > It has the following features: > 1. removes gengtype routines from coverage data Done. > 2. removes code from system headers (e.g., the host libstdc++) Likewise. > 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. Thanks, Martin > > I hope, you might find some of these ideas helpful. > > > On Tue, May 30, 2017 at 9:21 AM, Martin LiÅ¡ka <mliska@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 <mliska@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 >>> >> > > > ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-07-11 13:21 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-04-28 9:07 LCOV of current GCC Martin Liška 2017-04-28 9:38 ` Richard Biener 2017-04-28 15:39 ` Jeff Law 2017-04-28 17:16 ` Joseph Myers 2017-04-28 16:53 ` David Malcolm 2017-05-30 6:21 ` Martin Liška 2017-07-02 17:19 ` Mikhail Maltsev 2017-07-11 13:21 ` Martin Liška
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).