From: Paolo Bonzini <bonzini@gnu.org>
To: gcc-patches@gcc.gnu.org
Subject: Re: Use simplify_replace_rtx rather than wrap_constant
Date: Wed, 30 Sep 2009 13:49:00 -0000 [thread overview]
Message-ID: <4AC35B53.7080301@gnu.org> (raw)
Message-ID: <20090930134900.2zPopGabPth1nWGobe0H-ybjnBGR_aATi6-mWG7fXeM@z> (raw)
In-Reply-To: <87ljk1sr4c.fsf@firetop.home>
On 09/26/2009 04:44 PM, Richard Sandiford wrote:
> +/* Replace all occurrences of OLD_RTX in X with FN (DATA). Treat FN as
> + copy_rtx if it is null. Canonicalize and simplify the result. */
Richard, this is a great patch. The only objection is, I would pass X
to FN too. This way, if we have to build something out of X we can
avoid copying it unconditionally.
Paolo
next prev parent reply other threads:[~2009-09-30 13:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 16:15 Richard Sandiford
2009-09-26 21:11 ` Richard Sandiford
2010-01-09 20:37 ` H.J. Lu
2009-09-30 9:38 ` Alexandre Oliva
2009-09-30 20:23 ` Richard Sandiford
2009-09-30 12:45 ` Bernd Schmidt
2009-09-30 20:12 ` Richard Sandiford
2009-10-01 11:54 ` Bernd Schmidt
2009-10-01 21:05 ` Richard Sandiford
2009-10-05 14:23 ` Bernd Schmidt
2009-10-11 19:36 ` Richard Sandiford
2009-10-12 18:23 ` Richard Sandiford
2009-10-19 23:59 ` Bernd Schmidt
2009-10-21 15:53 ` Jakub Jelinek
2009-10-21 16:53 ` Jakub Jelinek
2009-10-21 17:13 ` [PATCH] " Jakub Jelinek
2009-10-21 20:13 ` Richard Sandiford
2009-10-21 22:17 ` Richard Sandiford
2009-10-21 17:26 ` Ulrich Weigand
2009-10-21 20:36 ` Richard Sandiford
2009-10-21 20:45 ` Jakub Jelinek
2009-10-21 21:25 ` Richard Sandiford
2009-10-21 22:01 ` Richard Sandiford
2009-10-22 17:17 ` Ulrich Weigand
2009-10-01 13:54 ` Eric Botcazou
2009-09-30 13:42 ` Paolo Bonzini [this message]
2009-09-30 13:49 ` Paolo Bonzini
2009-09-30 20:17 ` Richard Sandiford
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=4AC35B53.7080301@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).