From: "Alexander V. Bilichenko" <dmor@7ka.mipt.ru>
To: "Hacksaw" <hacksaw@hacksaw.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: GCC3.0 Produce REALLY slower code!
Date: Tue, 26 Jun 2001 04:29:49 +0400 [thread overview]
Message-ID: <000d01c0fdd7$1c416e60$d55355c2@microsoft> (raw)
In-Reply-To: <200106252330.f5PNUqE13722@habitrail.home.fools-errant.com>
There is not so much code in asm, so it's easy to patch code
the most reasonable method is to write parsing program for that
Best regards,
Alexander mailto:dmor@7ka.mipt.ru
------------------------------------------------------
Let's start the war, said Meggy
------------------------------------------------------
----- Original Message -----
From: "Hacksaw" <hacksaw@hacksaw.org>
To: "Alexander V. Bilichenko" <dmor@7ka.mipt.ru>;
<linux-kernel@vger.kernel.org>
Sent: Tuesday, June 26, 2001 3:30 AM
Subject: Re: GCC3.0 Produce REALLY slower code!
> >Here is link to Intel C compiler, that provide really faster code.
> >
> >http://developer.intel.com/software/products/compilers/linuxbeta.htm
>
> A quote from the site:
>
> * Not all of the GNU C language extensions, including the GNU inline
assembly
> format, are currently supported and, due to this, one cannot build the
Linux
> kernel with the beta release of the Intel compilers and the initial
product
> release.
>
>
next prev parent reply other threads:[~2001-06-26 0:30 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 ` GCC3.0 Produce REALLY slower code! Alexander V. Bilichenko
2001-06-25 23:30 ` Hacksaw
2001-06-26 0:29 ` Alexander V. Bilichenko [this message]
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='000d01c0fdd7$1c416e60$d55355c2@microsoft' \
--to=dmor@7ka.mipt.ru \
--cc=hacksaw@hacksaw.org \
--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