From: Rong Xu <xur@google.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>,
Xinliang David Li <xinliangli@gmail.com>,
Teresa Johnson <tejohnson@google.com>
Subject: Re: [PATCH] offline gcda profile processing tool
Date: Thu, 16 Jan 2014 17:30:00 -0000 [thread overview]
Message-ID: <CAF1bQ=TypsiC1Aa3Bz14cxX5sP9Zt02ecVPuU_xnS=2+zmDAQg@mail.gmail.com> (raw)
In-Reply-To: <CAF1bQ=T7xuC7O4=n90eN-pKh0me0d1e+50iXFtEcOD4o8s0ArQ@mail.gmail.com>
Ping.
-Rong
On Mon, Jan 13, 2014 at 12:43 PM, Rong Xu <xur@google.com> wrote:
> Hi,
>
> This patch implements gcov-tool, a offline profile processing tool.
> This version supports merging two profiles with weights, and scaling
> the profile with a floating-point / fraction weight.
>
> Earlier discussion can be found
> http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02631.html
>
> In the discussion of the earlier patch, Honza wanted a separated
> patch for interface change for gcov_merge_*() functions. In this patch,
> the changes for gcov_merge_*() are minimal by using a wrapper function.
> So I include everything in this patch.
>
> Tested with bootstrap profiledboostrap and SPEC2006 profiles.
>
> Thanks,
>
> -Rong
next prev parent reply other threads:[~2014-01-16 17:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 20:43 Rong Xu
2014-01-16 17:30 ` Rong Xu [this message]
2014-03-03 22:02 ` Rong Xu
2014-04-15 22:05 ` Jan Hubicka
2014-04-16 17:28 ` Rong Xu
2014-04-17 5:19 ` Jan Hubicka
2014-05-01 22:37 ` Rong Xu
2014-05-05 17:17 ` Rong Xu
2014-07-11 8:07 ` Richard Biener
2014-07-11 8:12 ` Christophe Lyon
2014-07-11 15:50 ` Xinliang David Li
2014-07-11 16:44 ` Rong Xu
2014-07-11 15:42 ` Xinliang David Li
2014-07-11 16:03 ` Jakub Jelinek
2014-07-11 16:13 ` Xinliang David Li
2014-07-11 16:48 ` Rong Xu
2014-07-11 18:30 ` Rong Xu
2014-07-11 18:46 ` Jan Hubicka
2014-07-11 18:53 ` Rong Xu
2014-07-13 7:49 ` Andreas Schwab
2014-05-15 20:37 ` Jan Hubicka
2014-05-20 22:59 ` Rong Xu
2014-05-25 23:43 ` Jan Hubicka
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='CAF1bQ=TypsiC1Aa3Bz14cxX5sP9Zt02ecVPuU_xnS=2+zmDAQg@mail.gmail.com' \
--to=xur@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=tejohnson@google.com \
--cc=xinliangli@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).