All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: Norberto Bensa <norberto+linux-kernel@bensa.ath.cx>
Cc: Norihiko Mukouyama <norihiko_m@jp.fujitsu.com>,
	Ingo at Pyrillion <ingo@pyrillion.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.3 patch for Intel Compiler 8.0
Date: Wed, 10 Mar 2004 02:52:47 +0100	[thread overview]
Message-ID: <404E74EF.1010204@stesmi.com> (raw)
In-Reply-To: <200403092156.57423.norberto+linux-kernel@bensa.ath.cx>

Norberto Bensa wrote:

> Norihiko Mukouyama wrote:
> 
>>Hi All!!
>>
>>
>>>Results: 33% of the lmbench procs faster on icc, 66% faster on gcc.
>>
>>If it is ture using icc 66% faster than gcc., It is wonderful.
>>Could you show us detail data to  lmbench results.
> 
> 
> I saw it the other way around: gcc is faster 66% of the time. Or did I read 
> wrong?

1/3 of the things are faster with icc. 2/3 of the things are faster
with gcc. Performance numbers not given.

// Stefan

  reply	other threads:[~2004-03-10  1:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 23:46 Kernel 2.6.3 patch for Intel Compiler 8.0 Ingo at Pyrillion
2004-03-10  0:08 ` Norberto Bensa
2004-03-10  0:17   ` Shawn
2004-03-10  0:18   ` AW: " Ingo at Pyrillion
2004-03-10  0:50     ` Norihiko Mukouyama
2004-03-10  0:56       ` Norberto Bensa
2004-03-10  1:52         ` Stefan Smietanowski [this message]
2004-03-10  2:08           ` Norihiko Mukouyama
2004-03-10  0:58       ` AW: " Ingo at Pyrillion
  -- strict thread matches above, loose matches on Subject: below --
2004-03-10  2:53 Nakajima, Jun
2004-03-12 22:31 Nakajima, Jun

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=404E74EF.1010204@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=ingo@pyrillion.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norberto+linux-kernel@bensa.ath.cx \
    --cc=norihiko_m@jp.fujitsu.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.