From: Arnaldo Carvalho de Melo <acme@mandriva.com>
To: Thiago Galesi <thiagogalesi@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org, lwn@lwn.net
Subject: Re: [ANNOUNCE] pahole and other DWARF2 utilities
Date: Tue, 31 Oct 2006 14:28:57 -0300 [thread overview]
Message-ID: <20061031172856.GE5319@mandriva.com> (raw)
In-Reply-To: <82ecf08e0610310805x6a77c2d3pd46eb2f76f75af67@mail.gmail.com>
On Tue, Oct 31, 2006 at 02:05:06PM -0200, Thiago Galesi wrote:
> >> Further ideas on how to use the DWARF2 information include tools
> >> that will show where inlines are being used, how much code is added by
> >> inline functions,
> >
> >It would be quite useful to be able to identify inlined functions which are
> >good candidates for uninlining.
> >
> >-
>
> Arnaldo, can't we get a call count for functions? (yes, it is not a
> run-time call count, but rather, how many times the function if called
> in the code) I guess this would help for this purpose of finding
> candidates for inlining, uninlining.
At least for inline expansions, yes, for normal function calls I have to
study more the DWARF2 documentation, but I guess its feasible.
- Arnaldo
next prev parent reply other threads:[~2006-10-31 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 21:33 [ANNOUNCE] pahole and other DWARF2 utilities Arnaldo Carvalho de Melo
2006-10-31 4:33 ` Andrew Morton
2006-10-31 16:05 ` Thiago Galesi
2006-10-31 17:28 ` Arnaldo Carvalho de Melo [this message]
2006-10-31 17:22 ` Arnaldo Carvalho de Melo
2006-10-31 20:45 ` Arnaldo Carvalho de Melo
2006-11-03 15:51 ` Arnaldo Carvalho de Melo
2006-11-03 19:07 ` Arnaldo Carvalho de Melo
2006-11-04 21:03 ` Top 100 inline functions (make allyesconfig) was " Arnaldo Carvalho de Melo
2006-11-05 6:30 ` Adrian Bunk
2006-11-05 16:42 ` Arnaldo Carvalho de Melo
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=20061031172856.GE5319@mandriva.com \
--to=acme@mandriva.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=thiagogalesi@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox