| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 30 Aug 2007 15:48:35 +0200 From: "Mohamed Bamakhrama" <bamakhrama@...il.com> To: "Jesper Juhl" <jesper.juhl@...il.com> Cc: linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org Subject: Re: Average number of instructions per line of kernel code On 8/30/07, Jesper Juhl <jesper.juhl@...il.com> wrote: > On 30/08/2007, Mohamed Bamakhrama <bamakhrama@...il.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. -- Mohamed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists