public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Ian Lance Taylor <iant@google.com>
Subject: Re: [patch] Split parts of cse_insn out to a few new functions
Date: Wed, 21 Mar 2012 23:15:00 -0000	[thread overview]
Message-ID: <CABu31nPQ_JGEDRPzy9qt3HFF6YCzA_-KSOVHQ6Z2qYe-t81xzg@mail.gmail.com> (raw)
In-Reply-To: <CABu31nPvRfLWD4aR4nMW+dA4WLK64yd2aeJTr=_aDdXWrgU8qQ@mail.gmail.com>

On Thu, Mar 22, 2012 at 12:09 AM, Steven Bosscher <stevenb.gcc@gmail.com> wrote:

>        (cse_find_path): Micro-optimization, reorder one condition to
>        avoid a reference to cfun.

Ah, and please ignore this bit. I don't know what I was thinking...

  reply	other threads:[~2012-03-21 23:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 21:07 Steven Bosscher
2012-03-21  0:14 ` Ian Lance Taylor
2012-03-21 23:10   ` Steven Bosscher
2012-03-21 23:15     ` Steven Bosscher [this message]
2012-03-26 19:02     ` Richard Sandiford
2012-03-26 19:13       ` Steven Bosscher

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=CABu31nPQ_JGEDRPzy9qt3HFF6YCzA_-KSOVHQ6Z2qYe-t81xzg@mail.gmail.com \
    --to=stevenb.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iant@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).