reload produces invalid address

reload produces invalid address

[Lars Brinkhoff]

Hello,

I'm working on a new backend, and I have noticed that in some
circumstances, the reload pass can produce invalid addresses.  Here's
an example:

Before reload:
  (insn 12 11 92 (set (reg/v:SI 24)
          (mem/s:SI (plus:SI (reg/v/f:SI 23)
                  (const_int 4 [0x4])) 1)) 43 {movsi} (nil)
      (nil))

After reload:
  (insn 12 11 92 (set (reg/v:SI 9 11 [25])
          (mem/s:SI (plus:SI (mem:SI (reg/f:SI 15 17) 0)
                  (const_int 4 [0x4])) 1)) 43 {movsi} (nil)
      (nil))

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?

-- 
http://lars.nocrew.org/

Re: reload produces invalid address

[Michael Matz]

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.