This is the mail archive of the gcc@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: vax optimization breakage?


On Sun, Jul 23, 2000 at 06:00:33PM -0600, Jeffrey A Law wrote:
> Thanks.  The problem is the jump optimizer is turning jump_insn 16 into
> a RETURN.

No, that's all kosher.  jump is allowed to make that transformation
any time HAVE_return is true.  Which for VAX is always.

The problem is that the LOOP_END note somehow fell below the
return insn.  This happens in .01.sibling, so presumably it
happened when running find_basic_blocks.  Anyway, the result
is that loop emits the cleanup code after the return, which
of course gets removed as dead code.


r~

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