From: "Ingo at Pyrillion" <ingo@pyrillion.org>
To: "'Nakajima, Jun'" <jun.nakajima@intel.com>,
"'Norihiko Mukouyama'" <norihiko_m@jp.fujitsu.com>,
"'Stefan Smietanowski'" <stesmi@stesmi.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 13:20:32 +0100 [thread overview]
Message-ID: <000301c4069a$15fd7980$374ca8c0@bunnybook2> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173FEB4C2@scsmsx402.sc.intel.com>
Hi Jun,
the patch I submitted is for icc 8.0, i.e. I386 platform only.
Did I understand your last message right that you even do not
need a kernel patch for icc, i.e. I386?
If so, then try to compile the 2.6.3 kernel using icc without
applying my patch and see what happens if icc "tries" to compile
hybrid code, i.e. mixed assembly and C statements....
The current icc 8.0 (and also icc 7.0) makes FATAL mistakes
compiling those mixings. Just check the object file that results
from "dec_and_lock.c" in arch/i386/lib using a disassembler.
Rgs, Ingo.
-----Ursprüngliche Nachricht-----
Von: Nakajima, Jun [mailto:jun.nakajima@intel.com]
Gesendet: Mittwoch, 10. März 2004 03:53
An: Norihiko Mukouyama; Stefan Smietanowski; Norberto Bensa
Cc: Ingo at Pyrillion; linux-kernel@vger.kernel.org
Betreff: RE: Kernel 2.6.3 patch for Intel Compiler 8.0
In 2.6, we already have sufficient changes for Intel IPF Compiler to
build the kernel, especially intrinscs changes, and you should not need
a patch. To make it faster, we might want to use PGO (profile guided
optimization) provided by the compiler; yes, it's available even for the
kernel with a driver.
Thanks,
Jun
>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
>owner@vger.kernel.org] On Behalf Of Norihiko Mukouyama
>Sent: Tuesday, March 09, 2004 6:08 PM
>To: Stefan Smietanowski; Norberto Bensa
>Cc: Ingo at Pyrillion; linux-kernel@vger.kernel.org
>Subject: RE: Kernel 2.6.3 patch for Intel Compiler 8.0
>
>Hi,Stefan!!
>
>>1/3 of the things are faster with icc. 2/3 of the things are faster
>>with gcc. Performance numbers not given.
>
>Thank you very much.
>I understood that meaning.
>
>By the way,
>
>I would like to learn the result of making his patch run on Itanium2.
>Because, the difference of the performance of the compiler being sure
to
>influence most
>remarkably.
>
>Can anyone try?
>
>Thanks.
>
>Norihiko
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-03-10 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 2:53 Nakajima, Jun
2004-03-10 12:20 ` Ingo at Pyrillion [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-10 0:50 Norihiko Mukouyama
2004-03-10 0:58 ` AW: " Ingo at Pyrillion
2004-03-10 0:08 Norberto Bensa
2004-03-10 0:18 ` 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='000301c4069a$15fd7980$374ca8c0@bunnybook2' \
--to=ingo@pyrillion.org \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=norberto+linux-kernel@bensa.ath.cx \
--cc=norihiko_m@jp.fujitsu.com \
--cc=stesmi@stesmi.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®