From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Not able to see all the symbols in the output of "nm" command
Date: Thu, 14 Apr 2011 13:11:33 +0100 [thread overview]
Message-ID: <BANLkTik7QWRZET-Eiup4PLarDqmaJ8Surw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimW+Zpp9hrWN+20_txiRnKamWPKJA@mail.gmail.com>
Hi Madhavi :)
On Thu, Apr 14, 2011 at 05:55, Madhavi Manchala <madhavi.linux@gmail.com> wrote:
> The functions which are available in the header file are "INLINE"
> functions.
I see. Well, think "inline" function like another form of macro. So,
they are inlined at the point they are called. This is different with
non inline function...they are called, most likely by executing "call"
instruction (in x86 assembly)
>However, there are few functions, which are available in
> the C files, also not able to see in the output of the "nm" command.
> Is there any idea?
Can you tell me their prototypes? just 2 or 3 of them? Quite likely
either they are explicitly inline function or decided by gcc to be
inlined because they are simple enough (thus "call" is considered a
bit expensive to do)
> Inlined functions are not visible in the output of the "nm" command.
> Is this known behaviour?
yes...if the function is inlined, there is no need to refer to the
function name (the symbol), right?
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-04-14 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 15:21 Not able to see all the symbols in the output of "nm" command Madhavi Manchala
2011-04-14 2:46 ` Mulyadi Santosa
2011-04-14 4:55 ` Madhavi Manchala
2011-04-14 12:11 ` Mulyadi Santosa [this message]
2011-04-14 13:21 ` Madhavi Manchala
2011-06-10 0:12 ` Gavin Guo
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=BANLkTik7QWRZET-Eiup4PLarDqmaJ8Surw@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).