This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: memrefs_conflict_p omission?
- To: law at cygnus dot com
- Subject: Re: memrefs_conflict_p omission?
- From: Richard Henderson <rth at cygnus dot com>
- Date: Tue, 7 Oct 1997 17:37:26 -0700
- Cc: John Carr <jfc at mit dot edu>, Richard Henderson <rth at cygnus dot com>, egcs at cygnus dot com
- References: <199710061344.JAA24923@no-knife.MIT.EDU> <6275.876264736@hurl.cygnus.com>
- Reply-To: Richard Henderson <rth at cygnus dot com>
> 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~