This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: side effects of the compiler-generated calls
- From: Tobias Schlüter <Tobias dot Schlueter at physik dot uni-muenchen dot de>
- To: David Livshin <david dot livshin at dalsoft dot com>
- Cc: fortran at gcc dot gnu dot org
- Date: Wed, 18 Jul 2007 15:07:42 +0200
- Subject: Re: side effects of the compiler-generated calls
- References: <469E092D.6040300@dalsoft.com>
David Livshin wrote:
gfortran generated code uses calls to routines with the names that begin
with “_gfortran_”, e.g. “_gfortran_set_std”, “_gfortran_st_write” etc.
What are the side effects of these routines? What registers are
used/affected by them? And most importantly, do they affect the value of
the stack pointer ( %esp )?
They are normal function calls in the C sense, so arguments are pushed
on the stack by the caller, and the caller pops them off the stack after
the callee has returned, so it's a bit of a matter of definition to say
if the call affects %esp or not, but the _callee_ will return it unchanged.
But maybe that's not your question, could you give more detail on what
you're trying to achieve?
Cheers,
- Tobi