public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "daniel.tian" <daniel.tian@mavrixtech.com.cn>
To: "'Jeff Law'" <law@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: RE: How to deal with unrecognizable RTL code
Date: Tue, 30 Jun 2009 14:22:00 -0000	[thread overview]
Message-ID: <20090630061736.42B0D3758001@mail.mavrixtech.com.cn> (raw)
In-Reply-To: <4A43C3F9.4080508@redhat.com>

> This looks like a different problem. What pass generates insn 17? What
> does insn 17 look like in the prior pass? If r14 is your stack/frame
> pointer, this might point to a problem in how your port interacts with
> register allocation/reload as reload can replace a pseudo with an
> equivalent memory location.
>
Exactly, But how do I prevent it, replacing a pseudo with an equivalent
memory location, happening.

	
Daniel Tian


  parent reply	other threads:[~2009-06-30  6:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  8:08 田晓南
2009-06-19 11:56 ` Paolo Bonzini
2009-06-24  9:35   ` daniel.tian
2009-06-24  9:36     ` Dave Korn
2009-06-24  9:37       ` Paolo Bonzini
2009-06-24 10:16         ` Dave Korn
2009-06-25 18:43 ` Jeff Law
2009-06-29 10:40   ` 答复: " daniel.tian
2009-07-01  1:57     ` Jeff Law
2009-06-29 10:52   ` daniel.tian
2009-06-29 21:11     ` How " Ian Lance Taylor
2009-06-30  6:20     ` Jim Wilson
2009-06-30 14:22   ` daniel.tian [this message]
2009-07-01  2:05     ` Jeff Law
     [not found] <5885251a0906190727p301b9122k7dcd235dcdd082a4@mail.gmail.com>
2009-06-22  1:56 ` daniel.tian
2009-06-22 11:21   ` Dave Korn
2009-06-24 12:42 daniel tian
2009-06-25 19:18 ` Jeff Law
2009-07-01  3:02 daniel.tian
2009-07-01  6:14 ` Jeff Law
2009-07-02  3:06   ` daniel.tian

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=20090630061736.42B0D3758001@mail.mavrixtech.com.cn \
    --to=daniel.tian@mavrixtech.com.cn \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.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).