mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: bamakhrama@gmail.com
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: Average number of instructions per line of kernel code
Date: Thu, 30 Aug 2007 15:31:12 +0200	[thread overview]
Message-ID: <9a8748490708300631o285fd31ch462199ec9535c6c2@mail.gmail.com> (raw)
In-Reply-To: <40378e40708300600h5837d46ci5266b8ae62bbd46e@mail.gmail.com>

On 30/08/2007, Mohamed Bamakhrama <bamakhrama@gmail.com> wrote:
> Hi all,
> I have a question regarding the average number of assembly
> instructions per line of kernel code. I know that this is a difficult
> question since it depends on many factors such as the instruction set
> architecture, compiler used, optimizations used, type of code, coding
> style, etc...
> I would like to know a rough estimate for such a quantity for the
> kernel 2.4/2.6 code running on MIPS32 architecture.
> My estimate is between 5-10 instructions. I googled for such a thing
> but couldn't find any useful papers/resources.
>

Why don't you simply count the number of non-blank non-comment lines
in the source files that you are building, build the kernel and then
count the number of instructions in the resulting binary ?

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2007-08-30 13:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 13:00 Mohamed Bamakhrama
2007-08-30 13:31 ` Jesper Juhl [this message]
2007-08-30 13:48   ` Mohamed Bamakhrama
2007-08-30 13:54     ` Jesper Juhl
2007-08-30 16:29     ` J. Scott Kasten
2007-08-30 19:49       ` Jan Engelhardt
2007-08-30 19:56         ` Freddy Spierenburg

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=9a8748490708300631o285fd31ch462199ec9535c6c2@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=bamakhrama@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.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

all inboxes | Powered by JetHome®