public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: Need kernel patch to compile with Intel compiler
Date: Thu, 12 May 2005 21:28:56 +0000	[thread overview]
Message-ID: <1115933336l.8448l.0l@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.61.0505121130030.31719@chaos.analogic.com> (from linux-os@analogic.com on Thu May 12 17:35:49 2005)


On 05.12, Richard B. Johnson wrote:
> On Thu, 12 May 2005, Tetsuji "Maverick" Rai wrote:
> 
> > In this mailing list archive I found a discussion on how to compile
> > kenrel 2.6.x with Intel C++ compiler, but it was a bit old, and only
> > kernel patch for version 2.6.5 or around so can be found.   As mine is
> > HT enabled, I want newer one.
> >
> > Does anyone know where to find it, or how to make it?
> >
> > regards,
> 
> The kernel is designed to be compiled with the GNU 'C' compler
> supplied with every distribution. It uses a lot of __asm__()
> statements and other GNU-specific constructions.
> 

The intel compiler supports all gcc syntax tweaks (__attribute__'s,
asm, cli options...) just because they want to be perfectly compatible
with gcc to compare/substitute...

> Why would you even attempt to convert the kernel sources to
> be compiled with some other tools? Also C++ won't work because
> the kernel is all about method, i.e., procedures. You need
> a procedural compiler for most of it, not an object-oriented
> one.

Intel's is a C/C++/Fortran compiler.

Last time I checked (a year or so ago) gcc catched the intel compiler
for equivalent options, or say it the other way, adjusting gcc options
you could get more or less the same performance. There were even places
where gcc generated faster code than icc. And that was gcc-3.0.x,
I think.

It is all a matter of knowing the default options that icc uses; the
big advantage (??) of icc was that it enabled the vectorizer by
default. And I think you could not allow streaming instructions
all over the kernel. I know they are used (raid) but I suppose it has
to be in a controlled way (does context switch preserve xmm registers ?).
And vector instructions are usefull just in very restricted situations.

It would be nice to redo the tests with gcc4/icc8 ;), now that gcc
has an auto-vectorizer.

In short, from my experience, I don't worry about icc. GCC is nice.

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandriva Linux release 2006.0 (Cooker) for i586
Linux 2.6.11-jam17 (gcc 4.0.0 (4.0.0-3mdk for Mandriva Linux release 2006.0))



  parent reply	other threads:[~2005-05-12 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12 14:46 Need kernel patch to compile with Intel compiler Tetsuji "Maverick" Rai
2005-05-12 15:35 ` Richard B. Johnson
2005-05-12 15:54   ` Chris Friesen
2005-05-13 13:50     ` Tetsuji "Maverick" Rai
2005-05-13 14:52       ` Matthias-Christian Ott
2005-05-12 21:28   ` J.A. Magallon [this message]
2005-05-16  0:57     ` Peter Chubb

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=1115933336l.8448l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.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