From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tom Rini <trini@ti.com>
Date: Tue, 14 Feb 2012 12:51:45 -0700
Subject: [U-Boot] [PATCH v3 6/6] SPL: Add README.omap3
In-Reply-To: <201202141343.28637.vapier@gentoo.org>
References: <1329174126-21460-1-git-send-email-trini@ti.com>
	<1329240581-7616-7-git-send-email-trini@ti.com>
	<201202141343.28637.vapier@gentoo.org>
Message-ID: <4F3ABB51.6080405@ti.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 02/14/2012 11:43 AM, Mike Frysinger wrote:
> On Tuesday 14 February 2012 12:29:41 Tom Rini wrote:
>> +Estimating stack usage
>> +----------------------
>
> isn't this usable for any target and not just omap3 ?

To a degree, yes.  If you try this on full u-boot instead it highlights 
some of the funny build things we do (there's still a handful of 
always-compiled-often-empty files like tqm8xx_pcmcia.c) and the lack of 
dealing with #ifdef's makes life real hard.

>> +With gcc 4.6 (and later) and the use of GNU cflow it is possible to
>> estimate stack usage at various points in run sequence of SPL.  The
>> -fstack-usage option to gcc will produce '.su' files (such as
>> arch/arm/cpu/armv7/syslib.su) that will give stack usage information and
>> cflow can construct program flow. +
>> +Must have gcc 4.6 or later, which supports -fstack-usage
>
> tools/checkpatch.pl is also pretty useful and doesn't require any compile
> version

checkstack.pl I assume you mean (which I posted the other week).  I 
believe it only reports 'large' usages whereas -fstack-usage reports all.

I'm not opposed to that also being merged of course, but it's just not 
the same :)

>> +$ for F in `cd spl; find  -name *.su`; do \
>> +	echo $F | sed -e 's/.su$/.c/'; done>  used-spl.list
>
> find spl -name '*.su' | sed -e 's:^spl/::' -e 's:[.]su$:.c:'>  used-spl.list
> -mike

Thanks.

-- 
Tom