[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-bugs
Subject:    Re: BOOTSTRAP FAILURE: segementation fault in genattrtab under hpux 10.20
From:       Richard Henderson <rth () redhat ! com>
Date:       2000-11-30 19:11:46
[Download RAW message or body]

On Wed, Nov 29, 2000 at 11:54:09PM -0700, Jeffrey A Law wrote:
> 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 remember looking at reorg, but jump uses returnjump_p,
which does considerably more than GET_CODE (pattern).

Quite a few ports are using

  [(return)
   (use (reg))]

I don't believe you'll run into a problem.

Of course, if you have conditional returns, you can't use this
form, since jump won't convert this.  You have to instead use
EPILOGUE_USES to keep the return register live.  This is one
of the reasons why I think the return rtx should be changed to

  (return <addr>)



r~

[prev in list] [next in list] [prev in thread] [next in thread]