From: "daniel.tian" <daniel.tian@mavrixtech.com.cn>
To: "'Jeff Law'" <law@redhat.com>
Cc: <gcc@gcc.gnu.org>, "'Peng Zheng'" <peng.zheng@mavrixtech.com>,
<thomas.liau@mavrixtech.com>
Subject: RE: How to deal with unrecognizable RTL code
Date: Thu, 02 Jul 2009 03:06:00 -0000 [thread overview]
Message-ID: <20090702030403.116973758001@mail.mavrixtech.com.cn> (raw)
In-Reply-To: <4A4AFEE3.8070004@redhat.com>
Hi, Jeff:
Thanks. I fixed the bug. The problem is in GO_IF_LEGITIMATE_ADDRESS. In
the reload processing, find_reload function will check the operand address
whether it is effective. I traced the function, and found my
GO_IF_LEGITIMATE_ADDRESS macro thought the following address is strict
legitimate address:
mem/s:SI (plus:SI (reg/v/f:SI 91 [ frame ])
(const_int 4 [0x4]))
Of course it is not a valid address in strict mode. And a logical error was
found in my rice_reg_ok_for_base function. After fixing it, cc1 works well .
Thank you very much!
Daniel.tian
_______________________________________________
Best Regards
Daniel Tian
Mavrix Technology, Inc.
Address：200 Zhangheng Road, #3501, Building 3, Zhangjiang Hi-tech Park,
Shanghai, P.R.China (201204)
Tel:86(21)51095958 - 8125
Fax:86(21)50277658
Email：daniel.tian@mavrixtech.com.cn
www.mavrixtech.com
next prev parent reply other threads:[~2009-07-02 3:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 3:02 daniel.tian
2009-07-01 6:14 ` Jeff Law
2009-07-02 3:06 ` daniel.tian [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-24 12:42 daniel tian
2009-06-25 19:18 ` Jeff Law
[not found] <5885251a0906190727p301b9122k7dcd235dcdd082a4@mail.gmail.com>
2009-06-22 1:56 ` daniel.tian
2009-06-22 11:21 ` Dave Korn
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: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
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=20090702030403.116973758001@mail.mavrixtech.com.cn \
--to=daniel.tian@mavrixtech.com.cn \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.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).