public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Leehod Baruch <LEEHOD@il.ibm.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: Question about merging two instructions.
Date: Mon, 22 Aug 2005 14:42:00 -0000	[thread overview]
Message-ID: <4309E41B.6090502@lu.unisi.ch> (raw)
In-Reply-To: <OF6BB453A0.91AAF632-ONC2257065.004BFE98-C2257065.004E32C4@il.ibm.com>


>Note that I don't want to replace any *def* and uses may appear in the 
>LHS.
>  
>
Ok, I see.  But you have to cope with *def*s appearing in the LHS: you 
don't want to replace them, yet your modified simplify_replace_rtx will!

>My plan was to use: replace_regs () to replace every use of (reg r)
>with the a new pseudo register (because this is the only function that
>I found that separates the uses from the defs)
>
Not really, as it will happily replace within a STRICT_LOW_PART, but 
that may as well be a bug.

I think you're best off making your own function for now.  And make it 
use validate_change so that you won't have to call recog manually.

Paolo

      reply	other threads:[~2005-08-22 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 13:52 Leehod Baruch
2005-08-21 16:55 ` Roger Sayle
2005-08-21 17:54   ` Leehod Baruch
2005-08-22  7:38     ` Paolo Bonzini
2005-08-22 13:33       ` Leehod Baruch
2005-08-22 13:37         ` Paolo Bonzini
2005-08-22 16:30           ` Richard Henderson
2005-08-22 13:49     ` Roger Sayle
2005-08-22  7:10   ` Paolo Bonzini
2005-08-22 14:12     ` Leehod Baruch
2005-08-22 14:42       ` Paolo Bonzini [this message]

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=4309E41B.6090502@lu.unisi.ch \
    --to=paolo.bonzini@lu.unisi.ch \
    --cc=LEEHOD@il.ibm.com \
    --cc=gcc@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).