From c3567d808df36d8a9e53f9cc9e6a1ac5d1e23195 Mon Sep 17 00:00:00 2001 From: Tom Rini Date: Wed, 15 Aug 2012 07:23:21 +0000 Subject: README.SPL: Move the 'Estimating stack usage' from omap3 to here The instructions are generic, so move to the generic doc. Signed-off-by: Tom Rini --- doc/README.SPL | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'doc/README.SPL') diff --git a/doc/README.SPL b/doc/README.SPL index bd375a01d9..5368586647 100644 --- a/doc/README.SPL +++ b/doc/README.SPL @@ -85,3 +85,26 @@ Debugging When building SPL with DEBUG set you may also need to set CONFIG_PANIC_HANG as in most cases do_reset is not defined within SPL. + + +Estimating stack usage +---------------------- + +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 + +1) Build normally +2) Perform the following shell command to generate a list of C files used in +SPL: +$ find spl -name '*.su' | sed -e 's:^spl/::' -e 's:[.]su$:.c:' > used-spl.list +3) Execute cflow: +$ cflow --main=board_init_r `cat used-spl.list` 2>&1 | $PAGER + +cflow will spit out a number of warnings as it does not parse +the config files and picks functions based on #ifdef. Parsing the '.i' +files instead introduces another set of headaches. These warnings are +not usually important to understanding the flow, however. -- cgit v1.2.3