From: Pavel Machek <pavel@suse.cz>
To: Andi Kleen <ak@suse.de>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
"David S. Miller" <davem@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org, "Mallick,
Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: Re: [PATCH] fixes for building kernel using Intel compiler
Date: Mon, 21 Oct 2002 11:21:27 +0200 [thread overview]
Message-ID: <20021021092127.GC2876@elf.ucw.cz> (raw)
In-Reply-To: <20021019042929.A18070@wotan.suse.de>
Hi!
> BTW do you have any benchmark / code size results to share with
> Intel compiler vs gcc 3.2 ? How much does it give ?
Also does it work properly after compiling with icc? Working well with
second compiler would be pretty good news for both kernel and icc...
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-10-26 10:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 2:17 [PATCH] fixes for building kernel using Intel compiler Nakajima, Jun
2002-10-19 2:29 ` Andi Kleen
2002-10-21 9:21 ` Pavel Machek [this message]
[not found] <A9EA4AD6F6B9D511BBED00508B66C69A04B37747@fmsmsx111.fm.intel.com>
2002-10-22 22:41 ` Suresh Siddha
-- strict thread matches above, loose matches on Subject: below --
2002-10-21 18:28 Ulrich Weigand
2002-10-19 1:16 Nakajima, Jun
2002-10-19 0:45 Nakajima, Jun
2002-10-19 1:02 ` Andi Kleen
[not found] <F2DBA543B89AD51184B600508B68D4000E6ADE5B@fmsmsx103.fm.intel.com.suse.lists.linux.kernel>
2002-10-19 0:07 ` Andi Kleen
2002-10-19 0:15 ` David S. Miller
2002-10-19 0:25 ` Andi Kleen
2002-10-18 23:48 Nakajima, Jun
2002-10-19 0:08 ` Greg KH
2002-10-21 12:48 ` Alan Cox
2002-10-21 15:56 ` Nakajima, Jun
2002-10-21 17:06 ` Brian Gerst
2002-10-22 6:09 ` Greg KH
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=20021021092127.GC2876@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=asit.k.mallick@intel.com \
--cc=davem@redhat.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunil.saxena@intel.com \
--cc=torvalds@transmeta.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.