memrefs_conflict_p omission?

[Richard Henderson]

> One thing to check is whether in any of
> the targets the argument pointer can be variable.  If so your change
> might not be safe.  The scheduler would not realize that the two
> memory references in
> 
> 	[arg pointer + 4] = x
> 	arg pointer += 4
> 	[arg pointer] = y

Nope.  It is always either eliminated to FP/SP, or is FP.  With the
exception of vax and we32k.  And vax doesn't change its AP, and I am
assuming we32k works the same way.  It doesn't appear to move...


r~