public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Xinliang David Li <davidxl@google.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
	 GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Simple change in dot dumper -- Display profile count and branch probability
Date: Mon, 22 Apr 2013 20:36:00 -0000	[thread overview]
Message-ID: <51758E2B.7040000@google.com> (raw)
In-Reply-To: <CAAkRFZJqZMOm7YWvfovKBMnENAJf9-nSg=zW68MDN1CgC1g41Q@mail.gmail.com>

On 2013-04-21 02:37 , Xinliang David Li wrote:
>          * graph.c (draw_cfg_node_succ_edges): Add branch probility as label.
>          * cfghhooks.c (dump_bb_for_graph): Dump profile count and frquency.
>          * Makefile.in: New dependency.

Looks OK.


Diego.

  reply	other threads:[~2013-04-22 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 20:36 Xinliang David Li
2013-04-21 20:54 ` Steven Bosscher
2013-04-21 21:17   ` Xinliang David Li
2013-04-22 20:36     ` Diego Novillo [this message]
2013-04-23  9:06       ` Xinliang David Li
2013-04-23 10:15         ` Richard Biener

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=51758E2B.7040000@google.com \
    --to=dnovillo@google.com \
    --cc=davidxl@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=stevenb.gcc@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).