From: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Which gcc version?
Date: Fri, 23 Nov 2001 10:02:50 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.33.0111230953170.18098-100000@shell1.aracnet.com> (raw)
In-Reply-To: <E167Jsj-00002C-00@DervishD>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1312 bytes --]
On Fri, 23 Nov 2001, [ISO-8859-1] Raúl[ISO-8859-1] Núñez de Arenas Coronado wrote:
> Sooner or later the kernel will need to be ported to gcc 3.x
> series, so, the sooner it gets tested with this compiler, the better.
One of the regression tests for gcc is to compile *a* Linux kernel, although
I have no clue which kernel they use, or if they just haul down the latest one
from the Internet.
> Anyway, if you have gcc 2.95.x installed onto your distro, use
> that for the kernel for maximum stability.
I haven't seen it on RH 7.x; I had to download and install it separately. And
it is a *royal* pain to get all the symbols/paths/libraries, etc., correct if
you want to use *anything* other than the default compiler/libraries/binutils
with Red Hat. One would need extreme motivation and extreme care.
For you (fellow) Athlon geeks, 2.95.x generates better code than either 2.96.x
or 3.0.x on the Atlas high-speed numerical linear algebra library. The reverse
is true for IA64; 3.0.x is about the only thing that generates decent code. If
that's motivating enough, have at it. YMMV.
--
znmeb@aracnet.com (M. Edward Borasky) http://www.aracnet.com/~znmeb
Relax! Run Your Own Brain with Neuro-Semantics!
http://www.aracnet.com/~znmeb/Flyer.htm
When puns are outlawed, only inlaws will have gnus.
next prev parent reply other threads:[~2001-11-23 18:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 17:12 RaúlNúñez de Arenas Coronado
2001-11-23 18:02 ` M. Edward (Ed) Borasky [this message]
2001-11-23 18:14 ` Thorsten Glaser
-- strict thread matches above, loose matches on Subject: below --
2001-11-23 12:53 Roy Sigurd Karlsbakk
2001-11-23 12:57 ` Arjan van de Ven
2001-11-23 13:51 ` war
2001-11-23 19:43 ` J Sloan
2001-11-23 13:59 ` Anton Altaparmakov
2001-11-23 14:11 ` war
2001-11-23 15:14 ` Arjan van de Ven
2001-11-23 15:30 ` Gábor Lénárt
2001-11-23 15:34 ` Arjan van de Ven
2001-11-23 19:50 ` J Sloan
2001-11-23 20:34 ` John Jasen
2001-11-23 21:55 ` J Sloan
2001-11-24 3:08 ` John Jasen
2001-11-24 12:24 ` Paul G. Allen
2001-11-26 18:31 ` Alan Cox
2001-11-27 8:42 ` Ahmed Masud
2001-11-23 16:10 ` Anton Altaparmakov
2001-11-23 14:43 ` Anton Altaparmakov
2001-11-23 16:23 ` Jeff Garzik
2001-11-23 18:30 ` Daniel Phillips
2001-11-23 18:56 ` Anton Altaparmakov
2001-11-23 19:28 ` Daniel Phillips
2001-11-23 20:14 ` Andrew Morton
2001-11-23 20:24 ` Anton Altaparmakov
2001-11-23 20:35 ` Andrew Morton
2001-11-23 21:09 ` David Weinehall
2001-11-24 16:01 ` Luigi Genoni
2001-11-24 16:09 ` Daniel Phillips
2001-11-24 17:32 ` Luigi Genoni
2001-04-05 10:56 which " Manoj Sontakke
2001-04-05 5:48 ` Alexander Viro
2001-04-05 14:09 ` Manoj Sontakke
2001-04-05 11:37 ` Bart Trojanowski
2001-04-05 12:02 ` Matti Aarnio
2001-04-05 12:26 ` David Woodhouse
2001-04-05 12:31 ` Matti Aarnio
2001-04-05 13:09 ` Richard B. Johnson
2001-04-05 11:45 ` Matti Aarnio
2001-04-05 11:50 ` christophe barbe
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=Pine.LNX.4.33.0111230953170.18098-100000@shell1.aracnet.com \
--to=znmeb@aracnet.com \
--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
all inboxes | Powered by JetHome®