Re: ppc glibc 2.3 failure

[Richard Henderson <rth at redhat dot com>]

On Mon, Oct 07, 2002 at 04:51:54PM -0700, Dale Johannesen wrote:
> >Is this the correct solution?
>
> Yes, I think so.  I ran into the same problem on Darwin and found
> the REG_MAYBE_DEAD notes as a way to identify code added in the prolog.

I don't think this is right.

Basically, the prologue has taken care of the link register.
This is clear from the fact that lr_save_p is false.  Thus it is
clear that if the epilogue emits any code to restore lr, that is
a bug.  We should not be hiding this bug by marking the prologue
instruction as maybe_dead.  It _isn't_ dead.  How can the epilogue
restore the link register if it wasn't saved in the prologue?

rs6000_stack_info needs to produce different results when called
during the reload loop (since we might be spilling more and more
registers), but after reload is complete, the values computed
must *never* change.

See ia64_compute_frame_size and how it handles "initialized".



r~