This is the mail archive of the gcc-patches@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: PREFERRED_STACK_BOUNDARY/function calling code fix

To: Jan Hubicka <hubicka at atrey dot karlin dot mff dot cuni dot cz>
Subject: Re: PREFERRED_STACK_BOUNDARY/function calling code fix
From: Richard Henderson <rth at cygnus dot com>
Date: Wed, 8 Mar 2000 14:59:00 -0800
Cc: Jason Merrill <jason at cygnus dot com>, grahams <grahams at rcp dot co dot uk>, egcs-patches at egcs dot cygnus dot com
References: <20000223165651.E32692@atrey.karlin.mff.cuni.cz> <38BAF586.FE2CABC8@rcp.co.uk> <20000301124026.A24452@atrey.karlin.mff.cuni.cz> <u97lflc4sk.fsf@yorick.cygnus.com> <20000303150114.A12574@atrey.karlin.mff.cuni.cz>

> I am not sure, if the sanity checking will pass on machines
> with parm_space, since stack adjustments necesary for parm_space are made
> there and it is not completely clear to me how this does this work.

It looks ok... I guess we'll have to see what triggers.

> 	* calls.c (expand_call): Do sanity checking on arg_space_so_far.
> 	Update arg_space_so_far on stack adjustments.
> 	(emit_library_call, emit_library_call_value): Likewise; take into
> 	account arg_space_so_far and pending_stack_adjust when calculcating
> 	the boundary.

Ok.


r~

References:
- Re: PREFERRED_STACK_BOUNDARY/function calling code fix
  - From: Jan Hubicka
- Re: PREFERRED_STACK_BOUNDARY/function calling code fix
  - From: Jason Merrill
- Re: PREFERRED_STACK_BOUNDARY/function calling code fix
  - From: Jan Hubicka

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