public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: 田晓南 <daniel.tian@mavrixtech.com.cn>
Cc: gcc@gcc.gnu.org, "'Peng Zheng'" <peng.zheng@mavrixtech.com>,
	        thomas.liau@mavrixtech.com,
	"'Ian Lance Taylor'" <iant@google.com>,
	        "'Michael Hope'" <michael.hope@gmail.com>
Subject: Re: How to deal with unrecognizable RTL code
Date: Fri, 19 Jun 2009 11:56:00 -0000	[thread overview]
Message-ID: <4A3B7CD9.4030702@gnu.org> (raw)
In-Reply-To: <20090619080614.207B750C9BEB@mail.mavrixtech.com.cn>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB2312, Size: 872 bytes --]

ÌïÏþÄÏ wrote:
> Hello, guys:
> 	The porting is really a difficult and huge job. So many things I
> don't know or miss result in countless bugs. 

It should not be hard.  You have to tell us however why this is
unrecognizable, that is, what would be the "closest" recognizable insn
supported by your port.

> (insn 264 191 193 15 (set (reg:HI 5 R5)
>         (subreg:HI (mem:SI (plus:SI (reg/f:SI 14 R14)
>                     (const_int 12 [0xc])) [0 crc+0 S4 A32]) 0)) -1 (nil)
>     (nil))
>
> (insn 261 197 200 14 (set (reg:HI 5 R5)
>         (subreg:HI (mem:SI (reg/f:SI 14 R14) [7 crc.16+0 S4 A32]) 0)) -1
> (nil)
>     (nil))

Also:

1) does your machine use cc0?

2) what pass is producing those subregs?

3) what is your definition of GO_IF_LEGITIMATE_ADDRESS?

[I trimmed a bit the list of recipients, sending to the mailing list is
usually enough.]

Paolo

  reply	other threads:[~2009-06-19 11:56 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 [this message]
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
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=4A3B7CD9.4030702@gnu.org \
    --to=bonzini@gnu.org \
    --cc=daniel.tian@mavrixtech.com.cn \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=michael.hope@gmail.com \
    --cc=peng.zheng@mavrixtech.com \
    --cc=thomas.liau@mavrixtech.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).