This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: pa.c clean-up
- To: Richard Henderson <rth at redhat dot com>
- Subject: Re: pa.c clean-up
- From: Jeffrey A Law <law at redhat dot com>
- Date: Wed, 31 Jan 2001 20:01:18 -0700
- cc: Alan Modra <alan at linuxcare dot com dot au>, gcc-patches at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <20010131183924.D14026@redhat.com>you write:
> On Wed, Jan 31, 2001 at 06:15:42PM -0700, Jeffrey A Law wrote:
> > That would indicate a problem elsewhere since there should have been
> > a dependency between the insn which adjusts the stack pointer and any
> > stores in the prologue which use the stack pointer in their address.
>
> Do you have special logic for functions that have a frame pointer
> as well?
I'm not sure what you mean by "special logic".
When we have a frame pointer our prologue looks something like this:
store return pointer into stack
copy fp, scratch
copy sp, fp
stwm scratch size(sp) /* store scratch into stack and allocate
stack space for new frame */
store other callee saved registers via fp
jeff