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: law at redhat dot com
- Subject: Re: PATCH 1: Re: BOOTSTRAP FAILURE: segementation fault in genattrtab
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- Date: Thu, 30 Nov 2000 13:45:28 -0500 (EST)
- Cc: gcc-bugs at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
> In message <200011210645.BAA15807@hiauly1.hia.nrc.ca>you write:
> > Is there a simple test to determine whether the frame pointer or other
> > eliminable register has been eliminated?
> I believe you can check FRAME_POINTER_NEEDED.
>
> > 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. If there was such code,
> > the hack in the pa.md probably would have broken long ago. Isn't the above
> > unnecessarily complicating things?'
> Possibly not. But better safe than sorry IMHO.
>
> > This gets even messier for the arg_pointer_rtx. On the pa 64 bit target,
> > the arg pointer isn't eliminable or always invariant, so the register could
> > be used for multiple purposes in a function.
> Yes. But if you look at how the arg pointer is handled in that case you'll
> find that it gets copied into a special pseudo.
I believe that the above issues are addressed in this revised patch which
I sent the other day: <http://gcc.gnu.org/ml/gcc-bugs/2000-11/msg00797.html>.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)