This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Reload Problem
- From: <tm_gccmail at kloo dot net>
- To: "C Jaiprakash, Noida" <cjaiprakash at noida dot hcltech dot com>
- Cc: gcc at gcc dot gnu dot org, Konark <konark_goel at yahoo dot com>
- Date: Sun, 16 May 2004 05:26:04 -0700 (PDT)
- Subject: Re: [RFC] Reload Problem
You may want to look at the SH target, as it has similar restrictions for
offsets.
Toshi
On Sat, 15 May 2004, C Jaiprakash, Noida wrote:
> Hi,
> No imputs from anybody? I thought gcc mailing list is the best place to
> get more and more educated in gcc.
>
> Regards,
> C Jaiprakash
>
> > Hi all,
> >
> > I am having a problem in legitimizing a reload
> > address. During the reload an address of
> > (plus:HI (reg/f:HI 24 R1) (const_int 130 [0x82] ))
> > is being generated, where the valid offset is only
> > 128. So in the legitimize reload i am breaking it up
> > as
> > (plus:HI (plus:HI (reg/f:HI 24 R1)
> > (const_int 127 [0x7f]))
> > (const_int 3 [0x3]))
> >
> > and then passing (plus:HI (reg/f:HI 24 R1)
> > (const_int 127 )) as the IN parameter (first
> > parameter) of the push_reload. There are only two
> > register R1 and R2 in this address class. I can not
> > have more than that. So this should get reloaded into
> > the register R2, but this is not happening. And
> > finally it gives an error of invalid address
> > (plus:HI (reg/f:HI 24 R1) (const_int 130 [0x82] ))
> >
> > Can someone tell me what maybe the problem? Another
> > point is that final memory access is in QI mode (can
> > this be the reason for the problem ?)
> >
> > Thanks and Regards
> > Konark
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> > http://movies.yahoo.com/showtimes/movie?mid=1808405861
> >
>
>
> Disclaimer:
>
> This message and any attachment(s) contained here are information that is
> confidential,proprietary to HCL Technologies and its customers, privileged
> or otherwise protected by law.The information is solely intended for the
> individual or the entity it is addressed to. If you are not the intended
> recipient of this message, you are not authorized to read, forward,
> print,retain, copy or disseminate this message or any part of it. If you
> have received this e-mail in error, please notify the sender immediately by
> return e-mail and delete it from your computer.
>
>
>