From: Marco Roeland <marco.roeland@xs4all.nl>
To: wsy@merl.com
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: compile-time error in 2.6.0-test9
Date: Sun, 26 Oct 2003 18:16:50 +0100 [thread overview]
Message-ID: <20031026171650.GD23792@localhost> (raw)
In-Reply-To: <200310261635.h9QGZTe13121@localhost.localdomain>
On Sunday 26 Oktober 2003 at 11:35 uur Bill Yerazunis wrote:
> What's the recommended version of GCC these days?
According to Documentation/Changes the 'bottomline' gcc (at least on
i386) is gcc 2.95.3 but 2.95.4 from Debian or 2.96 from RedHat and
Mandrake should be alright. A problem is that they are no longer
actively maintained so bugs aren't fixed. :-(
Just recently gcc 3.3.2 was released, so that or the latest from one's
distribution is 'current' and should work fine. Be warned though that
although they produce better code (and even that is sometimes disputed!)
and give better warnings, compilation is a lot slower.
The Linux kernel has a lot of handcrafted optimised code, so no gcc
version is going to outsmart that easily anyway, and also very important
is the amount of testing a kernel gets. Better a somewhat less optimal
compiler but which has had a lot of testing, and so has it bugs known
and 'workarounded', than a potential 'flyer' with unknown new bugs.
But for userspace applications I'd recommend gcc 3.x wholeheartedly,
for g++ especially.
--
Marco Roeland
next prev parent reply other threads:[~2003-10-26 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 15:53 compile-time error in 2.6.0-test9 wsy
2003-10-26 16:24 ` Marco Roeland
2003-10-26 16:35 ` wsy
2003-10-26 17:16 ` Marco Roeland [this message]
2003-10-26 23:19 ` wsy
2003-10-26 23:51 ` David Rees
2003-10-27 0:09 ` wsy
2003-10-27 2:26 ` Guy
2003-10-27 11:21 ` Ookhoi
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=20031026171650.GD23792@localhost \
--to=marco.roeland@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=wsy@merl.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