public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: "Richard Biener" <richard.guenther@gmail.com>,
	"Martin Liška" <mliska@suse.cz>
Cc: GCC Development <gcc@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: LCOV of current GCC
Date: Fri, 28 Apr 2017 16:53:00 -0000	[thread overview]
Message-ID: <1493398430.9106.158.camel@redhat.com> (raw)
In-Reply-To: <CAFiYyc0JgssAsC-7FOyhhPHKj70cQfrXxb+Vzdi=t+-oeUTe4A@mail.gmail.com>

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

  parent reply	other threads:[~2017-04-28 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  9:07 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 [this message]
2017-05-30  6:21     ` Martin Liška
2017-07-02 17:19       ` Mikhail Maltsev
2017-07-11 13:21         ` Martin Liška

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1493398430.9106.158.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).