Need "wrapper" to compile the Linux kernel with ICC

[TyMac]

I am a developer with an idea to start a new kernel source for Gentoo that is specifically for the Intel ICC compiler. Evidentally there is a "wrapper" that is needed to be applied to the kernel source first before ICC can correctly complie the Linux kernel. Where can I get this wrapper? (I have looked all over the web but the only yhing I can find is old documentation)

[TyMac]

We have a new story out on this project at Linux.com:

http://linux.com/news/software/linux-kernel/23770-compiler-project-aims-to-help-enterprise-it

[TyMac]

FYI we have a fast new patch out for 64bit 2.6.32 and .33 kernels:

wget http://www.linuxdna.com/dna-2.6.32.7-intel64-3.patch

wget http://www.linuxdna.com/dna-2.6.33-rc7-atom-intel64-2.patch

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.7.tar.bz2

wget http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.33-rc7.tar.bz2

It has been tested to work with the latest version 11.1.064 and .059 compilers and kernel 2.6.32.7. earlier .32 kernels *do not* work, fyi!

This patch also fixes a nagging issue with icc compiled modules not working.

Benchmakrs are avaiable at linuxdna.com

Techsupport can be submitted at:

http://groups.google.com/group/linuxdna

We are looking for developers who are intertested in working on the project! Please e-mail me at tyler@linuxdna.com if you are interested in any way contributing.

[blackburried]

The "-fno-builtin" is not working on icc 11.1.

It keeps changing struct initializations to "_intel_fast_memset". We don't call memset.

We tried making a gcc wrapper that included _intel_fast_memset, but its args are obviously not the same as w/ memset.

[blackburried]

Found the solution:

-ffreestanding

Thaidog: is that what you meant when you said:

[bash]This patch also fixes a nagging issue with icc compiled modules not working.[/bash]

... since I've moved on and my kernel modules still has some issues not present w/ gcc.

[Feilong_H_Intel]

blackburried,

Yes,-ffreestanding is what you need. You found it before I post this reply. :)

[blackburried]

Everything seems to be working properly, except, I'm n ot seeing the expected benefit in performance from the Intel compiler in the module I'm compiling.

I'm compiling the .c's into .o's w/ icc, but linking the .ko's w/ gcc.

I'm worried that whatever architecture-specifc code icc sets up to choose from at load time is not being properly done w/ my methodology.

IIRC, when not specifying a specific architecture, icc has to create optimized code for all architectures and make the choice of which code to select at load time.

When is this done, and/or how do I ensure this is being done?