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]
Other format: [Raw text]

Re: EH_RETURN_STACKADJ_RTX / EH_RETURN_DATA_REGNO vs. EH_RETURN_HANDLER_RTX / eh_return


> A target does not *need* the eh_return pattern if the usual
> epilogue code looks at current_function_calls_eh_return and if
> that's nonzero:
> 
> - adds EH_RETURN_STACKADJ_RTX to the stack-pointer.
> - restores all EH_RETURN_DATA_REGNO, even if they're
>   normally clobbered.

This is exactly what we arrived at on the pa.  I didn't know what I
was doing but it seems to work.  We couldn't use a eh_return pattern
because it is expanded too early.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


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