From: "Alexander V. Bilichenko" <dmor@7ka.mipt.ru>
To: "Tomasz Kłoczko" <kloczek@rudy.mif.pg.gda.pl>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: GCC3.0 Produce REALLY slower code!
Date: Mon, 25 Jun 2001 15:53:17 +0400 [thread overview]
Message-ID: <00e001c0fd6d$6bf42980$d55355c2@microsoft> (raw)
In-Reply-To: <Pine.LNX.4.21.0106251339370.13095-100000@rudy.mif.pg.gda.pl>
Here is link to Intel C compiler, that provide really faster code.
http://developer.intel.com/software/products/compilers/linuxbeta.htm
----- Original Message -----
From: "Tomasz Kłoczko" <kloczek@rudy.mif.pg.gda.pl>
To: "Alexander V. Bilichenko" <dmor@7ka.mipt.ru>
Sent: Monday, June 25, 2001 3:40 PM
Subject: Re: GCC3.0 Produce REALLY slower code!
> On Mon, 25 Jun 2001, Alexander V. Bilichenko wrote:
>
> > Although I just wanna say that there is no reason trying compile kernel
with
> > new shiny GCC 3.0 ;-). The result will be in kernel slowdown.
> >
> > Maybe, we can try to use Intel C compiler for some important ;-) (beta
> > version work with linux).
>
> Is there avalaible any free/evaluation version this compiler ?
>
> kloczek
> --
> -----------------------------------------------------------
> *Ludzie nie mają problemów, tylko sobie sami je stwarzają*
> -----------------------------------------------------------
> Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail:
kloczek@rudy.mif.pg.gda.pl*
>
next parent reply other threads:[~2001-06-25 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0106251339370.13095-100000@rudy.mif.pg.gda.pl>
2001-06-25 11:53 ` Alexander V. Bilichenko [this message]
2001-06-25 23:30 ` GCC3.0 Produce REALLY slower code! Hacksaw
2001-06-26 0:29 ` Alexander V. Bilichenko
2001-06-26 1:21 ` Hacksaw
2001-06-26 7:40 ` Thomas Pornin
2001-06-26 8:18 ` Hacksaw
2001-06-24 22:44 Alexander V. Bilichenko
2001-06-24 22:48 ` Rik van Riel
2001-06-24 23:46 ` Luigi Genoni
2001-06-25 9:33 ` Thomas Pornin
2001-06-24 23:19 ` Daniel Phillips
2001-06-25 9:16 ` Matthias Andree
2001-06-25 11:31 ` Alexander V. Bilichenko
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='00e001c0fd6d$6bf42980$d55355c2@microsoft' \
--to=dmor@7ka.mipt.ru \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
/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