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.