This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: BOOTSTRAP FAILURE: segementation fault in genattrtab under hpux 10.20



  In message <200011150304.WAA20806@hiauly1.hia.nrc.ca>you write:
  > > On Sun, Nov 12, 2000 at 02:49:29PM -0500, John David Anglin wrote:
  > > > > > As can be seen, the return pointer rp has been used as a scratch re
  > gister.
  > > > > > Its value at the first return is 0.
  > > > 
  > > > I added a `(use (reg:SI 2))' to the return insn to work around this pro
  > blem.
  > > 
  > > Hmm, it appears some general cleanup is needed in this area.
  > > Try the following.
  > 
  > Tried it.  The result was the same as with my hack (see below).
  > 
  > > > Another problem with regrename?
  > > 
  > > Dunno.. does it work with -fno-rename-registers?
  > 
  > Still have this problem.  Will try to dig deeper tomorrow.
  > 
  > Dave
  > -- 
  > J. David Anglin                                  dave.anglin@nrc.ca
  > National Research Council of Canada              (613) 990-0752 (FAX: 952-6
  > 605)
  > 
  > 2000-11-11  John David Anglin  <dave@hiauly1.hia.nrc.ca>
  > 
  > 	* pa.md (return, return_internal): Modify patterns to prevent regrename
  > 	mucking with the return pointer.
Err, umm.  Isn't this going to confuse reorg & jump.c's recognition of
return insns?  I believe they want to be able to do something like
GET_CODE (thingie) == RETURN?

I don't mind going forward with this patch, but we should have a plan for
dealing with jump & reorg.


jeff


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]