llvm dev - Jun 2004 - [LLVMdev] TargetFrameInfo: what's local area offset

The TargetFrameInfo, amoung other things, specifies "local area
offset" --
which, as comment say, is:

   the offset of the local area from the stack pointer on entrance to a
   function.

The question is -- what's local area? Is this the first stack location which
can be used by function for allocating its own variables?

- Volodya

On Mon, 7 Jun 2004, Vladimir Prus wrote:
>
> The TargetFrameInfo, amoung other things, specifies "local area
offset" --
> which, as comment say, is:
>
>    the offset of the local area from the stack pointer on entrance to a
>    function.
>
> The question is -- what's local area? Is this the first stack location
which
> can be used by function for allocating its own variables?
Yes, exactly.  The local area is the part that is local to the new
function invocation, where automatic variables, allocas, and spills go.

-Chris

-- 
http://llvm.cs.uiuc.edu/
http://www.nondot.org/~sabre/Projects/

Chris Lattner wrote:
> On Mon, 7 Jun 2004, Vladimir Prus wrote:
> > The TargetFrameInfo, amoung other things, specifies "local area
offset"
> > -- which, as comment say, is:
> >
> >    the offset of the local area from the stack pointer on entrance to
a
> >    function.
> >
> > The question is -- what's local area? Is this the first stack
location
> > which can be used by function for allocating its own variables?
>
> Yes, exactly.  The local area is the part that is local to the new
> function invocation, where automatic variables, allocas, and spills go.
Thanks. What would you say about the attached doc patch? It adds summary docs 
for the TargetFrameInfo class and clarifies what's local area is.

Thanks,
Volodya
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TargetFrameInfo.h.diff
Type: text/x-diff
Size: 814 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20040608/605a1cec/attachment.diff>