public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Rong Xu <xur@google.com>
Cc: reply@codereview.appspotmail.com, gcc-patches@gcc.gnu.org
Subject: Re: [google] limit excessive load/store motions (issue4563044)
Date: Fri, 10 Jun 2011 18:02:00 -0000	[thread overview]
Message-ID: <BANLkTi=G8kBKDkYoR7SKFtPE4vdwq-ZQ+w@mail.gmail.com> (raw)
In-Reply-To: <20110610174509.076F8C4159@rong.mtv.corp.google.com>

On Fri, Jun 10, 2011 at 10:45, Rong Xu <xur@google.com> wrote:
> Use a counter to avoid excessive load/store motions in tree and RTL level.
> This recovers some of the performance loss in FDO mode for openssl.

Rong, is this for trunk or google/main?  If it's for trunk, please
make sure you mark it as such.

OK for google/main for now.


Diego.

  reply	other threads:[~2011-06-10 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10 17:56 Rong Xu
2011-06-10 18:02 ` Diego Novillo [this message]
2011-06-10 18:17   ` Rong Xu
2011-06-10 18:29 davidxl

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='BANLkTi=G8kBKDkYoR7SKFtPE4vdwq-ZQ+w@mail.gmail.com' \
    --to=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=reply@codereview.appspotmail.com \
    --cc=xur@google.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).