| To: | bamakhrama@gmail.com |
|---|---|
| Subject: | Re: Average number of instructions per line of kernel code |
| From: | "Jesper Juhl" <jesper.juhl@gmail.com> |
| Date: | Thu, 30 Aug 2007 15:54:45 +0200 |
| Cc: | linux-mips@linux-mips.org, linux-kernel@vger.kernel.org |
| Dkim-signature: | a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=t00tLg4hanCCJpHrxNbTqYW3zXt14MbTqRQVns9XfzA/dIc1C+WrseF8yFGEm9m5zxFz9pYtkEEks/FzPnMMEpJlBvrk5zqsyjTnDGMiZ+AR5DZOU9DDY23Wb7bB3QA8MKGf8HBPN/px8TUKaOygXGaQ+w6a85BwvSu6bDUZ4HU= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SpNELESd/puH31vf5cVeG9niayGHzSGLVrWI3I/x8L7H8dWsWA1SbZwu8seNSTaOUKN5yxRZmNflH0nu0B2Z4zvdxrRa5IeBXf6Z2hX6HXHwQuy/Sz26K2YinAVuvO3wKUO/4AaAy+lKm/pIURoNWz/DpSlYPMtF7PEQJqC9UdM= |
| In-reply-to: | <40378e40708300648i4f016906v60f821bf182a5633@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <40378e40708300600h5837d46ci5266b8ae62bbd46e@mail.gmail.com> <9a8748490708300631o285fd31ch462199ec9535c6c2@mail.gmail.com> <40378e40708300648i4f016906v60f821bf182a5633@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On 30/08/2007, Mohamed Bamakhrama <bamakhrama@gmail.com> wrote: > On 8/30/07, Jesper Juhl <jesper.juhl@gmail.com> wrote: > > 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 ? > > Hi, > I agree with you but is there any way to include ALL the drivers in > the kernel tree in building the image? Otherwise, I will be counting > un-used lines. > make allyesconfig make -- 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Average number of instructions per line of kernel code, Mohamed Bamakhrama |
|---|---|
| Next by Date: | Re: problem about the tool chain for R3000, David Daney |
| Previous by Thread: | Re: Average number of instructions per line of kernel code, Mohamed Bamakhrama |
| Next by Thread: | Re: Average number of instructions per line of kernel code, J. Scott Kasten |
| Indexes: | [Date] [Thread] [Top] [All Lists] |