This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How to deal with unrecognizable RTL code
- From: Jeff Law <law at redhat dot com>
- To: "daniel.tian" <daniel dot tian at mavrixtech dot com dot cn>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 30 Jun 2009 20:06:09 -0600
- Subject: Re: How to deal with unrecognizable RTL code
- References: <20090630061736.42B0D3758001@mail.mavrixtech.com.cn>
daniel.tian wrote:
>> 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.
>
I'd start by looking at your GO_IF_LEGITIMATE_ADDRESS macro and/or trace
find_reloads for the problematic insn.
jeff