This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH 1: Re: BOOTSTRAP FAILURE: segementation fault in genattrtab
- To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
- Subject: Re: PATCH 1: Re: BOOTSTRAP FAILURE: segementation fault in genattrtab
- From: Bernd Schmidt <bernds at redhat dot com>
- Date: Tue, 21 Nov 2000 11:31:14 +0000 (GMT)
- cc: law at redhat dot com, gcc-bugs at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Jeff Law wrote:
> > It seems to me that we should return the hard frame pointer if it is
> > being used that way. Else we should not.
> >
> > ie, if we did not eliminate the frame pointer, then returning frame_pointer_rtx
> > would be the right thing to do.
> >
> > If we did eliminate the frame pointer, then we do not want to return
> > frame_pointer_rtx.
On Tue, 21 Nov 2000, John David Anglin wrote:
> Is there a simple test to determine whether the frame pointer or other
> eliminable register has been eliminated?
frame_pointer_needed might do it.
> When I wrote the patch, I assumed
> that no code would call gen_rtx_REG if it needed the frame_pointer_rtx
> after reload even if it hadn't been eliminated.
I believe this assumption is correct. If you want the frame pointer register,
you should be using frame_pointer_rtx rather than calling gen_rtx_REG. The
code in gen_rtx_REG is simply a workaround for the insn-emit.c.
Bernd