All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [RFC v2 0/4] scripts: add stack{usage,delta} scripts
Date: Wed, 19 Aug 2015 16:16:25 +0200	[thread overview]
Message-ID: <55D48FB9.50605@suse.cz> (raw)
In-Reply-To: <1435220492-15868-1-git-send-email-linux@rasmusvillemoes.dk>

On 2015-06-25 10:21, Rasmus Villemoes wrote:
> The current checkstack.pl script has a few problems, stemming from the
> overly simplistic attempt at parsing objdump output with regular
> expresions. Since gcc 4.6 introduced the -fstack-usage option, we can
> now get the exact stack use instead of resorting to ad hoc methods.
> 
> This introduces two small scripts. One for running make with KCFLAGS
> set to -fstack-usage, followed by collecting the generated .su files
> in a single output file. Another for taking two such output files and
> computing the changes in stack use.
> 
> 2/4 and 3/4 may be too small by themselves; they can easily be
> squashed into 1/4.
> 
> v2: Use KCFLAGS instead of EXTRA_CFLAGS. A few more details in commit
> messages. Simpler option handling in stackusage. Removed accidental
> leftover debug prints.

Do you plan any new iterations, or is this final despite the [RFC]? If
it's final, I will apply it.

Michal

  parent reply	other threads:[~2015-08-19 14:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  1:10 [RFC 0/4] scripts: add stack{usage,delta} scripts Rasmus Villemoes
2015-06-21  1:10 ` [RFC 1/4] scripts: add stackusage script Rasmus Villemoes
2015-06-21  1:10   ` Rasmus Villemoes
2015-06-23 13:53   ` Michal Marek
2015-06-25  8:04     ` Rasmus Villemoes
2015-06-21  1:10 ` [RFC 2/4] .gitignore: add *.su pattern Rasmus Villemoes
2015-06-21  1:10   ` Rasmus Villemoes
2015-06-21  1:10 ` [RFC 3/4] kbuild: remove *.su files generated by -fstack-usage Rasmus Villemoes
2015-06-21  1:10   ` Rasmus Villemoes
2015-06-21  1:10 ` [RFC 4/4] scripts: add stackdelta script Rasmus Villemoes
2015-06-21  1:10   ` Rasmus Villemoes
2015-06-22  7:39   ` Rasmus Villemoes
2015-06-22  7:39     ` Rasmus Villemoes
2015-06-25  8:21 ` [RFC v2 0/4] scripts: add stack{usage,delta} scripts Rasmus Villemoes
2015-06-25  8:21   ` [RFC v2 1/4] scripts: add stackusage script Rasmus Villemoes
2015-06-25  8:21   ` [RFC v2 2/4] .gitignore: add *.su pattern Rasmus Villemoes
2015-06-25  8:21   ` [RFC v2 3/4] kbuild: remove *.su files generated by -fstack-usage Rasmus Villemoes
2015-06-25  8:21   ` [RFC v2 4/4] scripts: add stackdelta script Rasmus Villemoes
2015-08-19 14:16   ` Michal Marek [this message]
2015-08-20  9:53     ` [PATCH v3 0/4] scripts: add stack{usage,delta} scripts Rasmus Villemoes
2015-08-20  9:53       ` [PATCH v3 1/4] scripts: add stackusage script Rasmus Villemoes
2015-08-20  9:53       ` [PATCH v3 2/4] .gitignore: add *.su pattern Rasmus Villemoes
2015-08-20  9:53       ` [PATCH v3 3/4] kbuild: remove *.su files generated by -fstack-usage Rasmus Villemoes
2015-08-20  9:53       ` [PATCH v3 4/4] scripts: add stackdelta script Rasmus Villemoes
2015-08-28 15:05       ` [PATCH v3 0/4] scripts: add stack{usage,delta} scripts Michal Marek

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=55D48FB9.50605@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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.