Invalid alias info through crossjumping

[Michael Matz]

Hi,

On Mon, 2 Feb 2004, Andreas Krebbel wrote:

> I could imagine two solutions to fix this:
> 
> 1.) The insn comparison during crossjumping analysis should draw the
>     alias information into. Two insns with different alias data should
>     never be considered "mergable".
> 
> 2.) If insns get merged during crossjumping the memory reference in the
>     resulting insn must be marked with a general alias constraint.

Each has its merits.  I feel, that 1 would be the safer approach.  
Currently insn_match_p() uses rtx_equal_p() and that one doesn't look into 
the second slot of MEM exprs.  I'm not sure if that's a good idea.


Ciao,
Michael.