This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: reload produces invalid address
- To: Lars Brinkhoff <lars at nocrew dot org>
- Subject: Re: reload produces invalid address
- From: Michael Matz <matzmich at cs dot tu-berlin dot de>
- Date: Sat, 9 Jun 2001 04:54:41 +0200 (MET DST)
- cc: <gcc at gcc dot gnu dot org>
Hi,
On 8 Jun 2001, Lars Brinkhoff wrote:
> The old address (plus:SI (reg:SI 23) (const_int 4)) was a valid address,
> but the new address (plus:SI (mem:SI (reg:SI 15)) (const_int 4)) is not
> a valid address according to GO_LEGITIMATE_ADDRESS_P in my backend.
>
> How do I avoid this?
Could it be, that reload is doing this initially because of a wrong
setting of supported number of indirection on your platform? (This
basically tells reload how many nested (mem)'s are possible) (See
spill_indirect_level in reload.c and it's computation in init_reload()).
OTOH I may be way off.
Ciao,
Michael.