This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Stack implementation
- To: Aaron <anp1 at cec dot wustl dot edu>
- Subject: Re: Stack implementation
- From: Alan Lehotsky <apl at alum dot mit dot edu>
- Date: Mon, 2 Jul 2001 12:19:23 -0400
- Cc: Alan Lehotsky <apl at alum dot mit dot edu>, Toshi Morita <tm2 at best dot com>, gcc-bugs at gcc dot gnu dot org
- References: <Pine.SOL.3.96.1010702080849.19627B-100000@clarion.cec.wustl.edu>
At 8:21 AM -0500 7/2/01, Aaron wrote:
> >
>> The stack-frame is target-dependent and as such is primarily documented by the code in the target.h
>> and target.c files. These parameterize the call-return, argument passing and automatic storage
>> mechanisms on a per-target basis.
>
>Aren't the target.h and target.c part of the g77 Fortran compiler and not
>the C compiler?
That was <meta>-target, e.g., in your case
gcc/config/i386/i386.c and i386.h
>
>
>I'm using a PentiumIII running Red Hat 7.1. (gcc 2.96-81). I'm looking to
>understand how the memory is allocated on the call stack when a function
>is called. I am specifically interested in finding the purpose, size, and
>location of all the fields stored in each frame (parameters, stack
>pointer?, return address, variables).
As Obi-wan said.....
Use the source, Luke!
See also function.c and calls.c for the gory details.....
-- Al
>
>Aaron
--
------------------------------------------------------------------------
Quality Software Management
http://home.earthlink.net/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
(978)287-0436 Fax
Software Process Improvement and Management Consulting
Language Design and Compiler Implementation