From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 6/6] SPL: Add README.omap3
Date: Tue, 14 Feb 2012 12:51:45 -0700 [thread overview]
Message-ID: <4F3ABB51.6080405@ti.com> (raw)
In-Reply-To: <201202141343.28637.vapier@gentoo.org>
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
next prev parent reply other threads:[~2012-02-14 19:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 22:58 [U-Boot] [PATCH 1/6] .gitignore: Add .su files Tom Rini
2012-02-08 22:58 ` [U-Boot] [PATCH 2/6] config.mk: Make cc-option create a file under include/generated Tom Rini
2012-02-08 22:58 ` [U-Boot] [PATCH 3/6] arm: Check for -fstack-usage support Tom Rini
2012-02-13 22:30 ` Wolfgang Denk
2012-02-08 22:58 ` [U-Boot] [PATCH 4/6] spl.c: Use __noreturn decorator Tom Rini
2012-02-08 22:58 ` [U-Boot] [PATCH 5/6] README: Add more SPL config options Tom Rini
2012-02-08 22:58 ` [U-Boot] [PATCH 6/6] SPL: Add README.omap3 Tom Rini
2012-02-08 23:08 ` Peter Meerwald
2012-02-08 23:19 ` Tom Rini
2012-02-09 3:36 ` [U-Boot] [PATCH 1/6] .gitignore: Add .su files Mike Frysinger
2012-02-13 23:02 ` [U-Boot] [PATCH v2 0/6] SPL-related documentation / checking Tom Rini
2012-02-14 17:29 ` [U-Boot] [PATCH v3 " Tom Rini
2012-02-14 17:29 ` [U-Boot] [PATCH v3 1/6] .gitignore: Add .su files Tom Rini
2012-02-14 17:29 ` [U-Boot] [PATCH v3 2/6] config.mk: Make cc-option create a file under include/generated Tom Rini
2012-02-14 17:29 ` [U-Boot] [PATCH v3 3/6] config.mk: Check for -fstack-usage support Tom Rini
2012-02-20 23:50 ` [U-Boot] [PATCH v4 " Tom Rini
2012-02-14 17:29 ` [U-Boot] [PATCH v3 4/6] spl.c: Use __noreturn decorator Tom Rini
2012-02-14 17:29 ` [U-Boot] [PATCH v3 5/6] README: document more SPL config options Tom Rini
2012-02-14 17:29 ` [U-Boot] [PATCH v3 6/6] SPL: Add README.omap3 Tom Rini
2012-02-14 18:43 ` Mike Frysinger
2012-02-14 19:51 ` Tom Rini [this message]
2012-02-20 23:27 ` [U-Boot] [PATCH v4 " Tom Rini
2012-02-13 23:02 ` [U-Boot] [PATCH v2 1/6] .gitignore: Add .su files Tom Rini
2012-02-13 23:02 ` [U-Boot] [PATCH v2 2/6] config.mk: Make cc-option create a file under include/generated Tom Rini
2012-02-14 5:43 ` Mike Frysinger
2012-02-14 14:35 ` Tom Rini
2012-02-13 23:02 ` [U-Boot] [PATCH v2 3/6] config.mk: Check for -fstack-usage support Tom Rini
2012-02-14 5:39 ` Mike Frysinger
2012-02-13 23:02 ` [U-Boot] [PATCH v2 4/6] spl.c: Use __noreturn decorator Tom Rini
2012-02-14 5:39 ` Mike Frysinger
2012-02-13 23:02 ` [U-Boot] [PATCH v2 5/6] README: Add more SPL config options Tom Rini
2012-02-14 5:40 ` Mike Frysinger
2012-02-13 23:02 ` [U-Boot] [PATCH v2 6/6] SPL: Add README.omap3 Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F3ABB51.6080405@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.