From: "Ingo at Pyrillion" <ingo@pyrillion.org>
To: "'Norihiko Mukouyama'" <norihiko_m@jp.fujitsu.com>,
"'Norberto Bensa'" <norberto+linux-kernel@bensa.ath.cx>
Cc: <linux-kernel@vger.kernel.org>
Subject: AW: Kernel 2.6.3 patch for Intel Compiler 8.0
Date: Wed, 10 Mar 2004 01:58:51 +0100 [thread overview]
Message-ID: <000201c4063a$db038f90$374ca8c0@bunnybook2> (raw)
In-Reply-To: <FLEBKJHLJPMMOPBNJGELCEMMCNAA.norihiko_m@jp.fujitsu.com>
Hi again,
please read my last mail carefully:
"33% procs faster on icc, 66% faster on gcc"
means that gcc (GNU) is superior. But the patch is a preliminary
version...
greetings, Ingo.
-----Ursprüngliche Nachricht-----
Von: Norihiko Mukouyama [mailto:norihiko_m@jp.fujitsu.com]
Gesendet: Mittwoch, 10. März 2004 01:50
An: Ingo at Pyrillion; 'Norberto Bensa'
Cc: linux-kernel@vger.kernel.org
Betreff: RE: Kernel 2.6.3 patch for Intel Compiler 8.0
Hi All!!
>I used the patch to compile two identical kernels with gcc 3.3.3 and
>icc 8.0 with oprofile support built in. The optimization switches were
>chosen quite conservative, i.e. "-O2 -Ob1", no IPO, and of course: no
>MMX, SSE, and SSE2 stuff inside the kernel (thus disabling Intel's
>great vectorizer).
>Profiling: lmbench ran ten times but time measurements were taken from
>oprofile (on Pentium 4, GLOBAL_POWER_EVENTS in kernel space only,
>counter overflow: 3.000).
>Results: 33% of the lmbench procs faster on icc, 66% faster on gcc.
Really???
If it is ture using icc 66% faster than gcc., It is wonderful.
Could you show us detail data to lmbench results.
Thanks!!
Norihiko
next prev parent reply other threads:[~2004-03-10 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 23:46 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
2004-03-10 2:08 ` Norihiko Mukouyama
2004-03-10 0:58 ` Ingo at Pyrillion [this message]
2004-03-10 2:53 Nakajima, Jun
2004-03-10 12:20 ` AW: " Ingo at Pyrillion
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='000201c4063a$db038f90$374ca8c0@bunnybook2' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®