This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ACCUMULATE_OUTGOING_ARGS/PUSH_ROUNDING as runtime switch
- To: Richard Henderson <rth at cygnus dot com>
- Subject: Re: ACCUMULATE_OUTGOING_ARGS/PUSH_ROUNDING as runtime switch
- From: Jan Hubicka <hubicka at atrey dot karlin dot mff dot cuni dot cz>
- Date: Sun, 30 Jan 2000 22:38:33 +0100
- Cc: egcs-patches at egcs dot cygnus dot com
- References: <20000130011906.B32728@atrey.karlin.mff.cuni.cz> <20000130111318.B14961@cygnus.com>
> On Sun, Jan 30, 2000 at 01:19:06AM +0100, Jan Hubicka wrote:
> > This patch changes ACCUMULATE_OUTGOING_ARGS and PUSH_ROUNDING to runtime
> > choosable options. The ACCUMULATE_OUTGOING_ARGS is now expression and
> > PUSH_ROUNDING is handled by new target macro PUSH_ARGS (when nonzero, push
> > instructions are used, otherwise discrete equivalent).
>
> I don't think I understand. Isn't PUSH_ARGS == !ACCUMULATE_OUTGOING_ARGS?
As I understood the code, it is able to do !PUSH_ARGS and
!ACCUMULATE_OUTGOING_ARGS prologues/epilogues as well. It just does stack
manipulation by hand(so it adjusts stack before and after every call) and is
default on some architectures. (SH I believe)
I can change PUSH_ARGS to !ACCUMULATE_OUTGOING_ARGS if you this this alternative
don't make sense.
I think it can be usefull for platofrms that use ACCUMULATE_OUTGOING_ARGS by
default but someone want to squeze out few bytes from frame sizes.
Honza