xfs
[Top] [All Lists]

Re: Large Stack Usage in One More Function

To: Steve Lord <lord@xxxxxxx>
Subject: Re: Large Stack Usage in One More Function
From: Danny Cox <danscox@xxxxxxxxxxxxxx>
Date: 27 Aug 2002 13:22:52 -0400
Cc: XFS Mailing List <linux-xfs@xxxxxxxxxxx>
In-reply-to: <1030467882.16697.28.camel@xxxxxxxxxxxxxxxxxxxx>
References: <1030467482.1611.14.camel@wiley> <1030467882.16697.28.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Steve,

On Tue, 2002-08-27 at 13:04, Steve Lord wrote:
> Probably not just the vattr_t, most of the function is a large switch
> statement, and each case in there has its own on the stack variables.
> If the compiler is not being smart about it they would each get
> their own non-overlapping space.

        Actually, I wondered about that, too (what the compiler does with temp
vars in {} blocks).

        The script is attached.  It requires the Disassemble and the blib
modules.  blib is included with the Disassemble module, and is available
from CPAN @

http://search.cpan.org/author/BOBMATH/Disassemble-X86-0.12/X86.pm

-- 
kernel, n.: A part of an operating system that preserves the
medieval traditions of sorcery and black art.

Danny


-- Binary/unsupported file stripped by Ecartis --
-- Type: text/x-perl
-- File: check_stack



<Prev in Thread] Current Thread [Next in Thread>