All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias-Christian Ott <matthias.christian@tiscali.de>
To: "Tetsuji \"Maverick\" Rai" <tetsuji.rai@gmail.com>
Cc: Chris Friesen <cfriesen@nortel.com>,
	linux-os@analogic.com, linux-kernel@vger.kernel.org
Subject: Re: Need kernel patch to compile with Intel compiler
Date: Fri, 13 May 2005 16:52:44 +0200	[thread overview]
Message-ID: <4284BF3C.4030501@tiscali.de> (raw)
In-Reply-To: <377362e105051306506e3870a6@mail.gmail.com>

Tetsuji "Maverick" Rai wrote:
> On 5/13/05, Chris Friesen <cfriesen@nortel.com> wrote:
> 
>>Richard B. Johnson wrote:
>>
>>
>>>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.
>>
>>Yep.  And Intel added a bunch of them to their compiler so that they
>>could build a kernel with it.
>>
>>
>>>Why would you even attempt to convert the kernel sources to
>>>be compiled with some other tools?
>>
>>The Intel compiler is quite good at optimizing for their processors (and
>>ironically for AMD ones as well).  However, I think that a lot of the
>>gains come from the vectorizer, which of course can't be used with
>>kernel code.
>>
>>Chris
>>
> 
> 
> Yes, that's why I wanted to use Intel's compiler for kernel (of course
> I didn't mean to use C++; the product's name is C++, it doesn't sell C
> alone.)    Its vectorization is so nice that SETI@home calculates
> 20-30% faster than the original one compiled with gcc.
> 
> But I thought it's not such a good idea to build kernel with Intel
> compiler, because kernel's speed doesn't affect so much in my case. 
> And that vectorization isn't so effective in kernel.  PGO (profile
> guided optimization) is the only effective optimization in the kernel
> according to
> http://softwareforums.intel.com/ids/board/message?board.id=16&message.id=1504
> 
> So I decided not to try this...looks like too much effort and little
> gain.  and I guess that's why nobody is trying this now.
> 
Yeah that's what the 2.6.5 patch does. Some People talked about 20% more speed with this patch last year. If anyone is 
able to patch the current kernel the patch should be in -mm.

Matthias-Christian Ott

  reply	other threads:[~2005-05-13 14:53 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 [this message]
2005-05-12 21:28   ` J.A. Magallon
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=4284BF3C.4030501@tiscali.de \
    --to=matthias.christian@tiscali.de \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=tetsuji.rai@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.