From: Dan Kegel <dank@kegel.com>
To: John Bradford <john@grabjohn.com>, linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler version
Date: Sat, 29 May 2004 07:42:41 -0700 [thread overview]
Message-ID: <40B8A161.5040306@kegel.com> (raw)
John B. wrote:
> Quote from Adrian Bunk <bunk@fs.tum.de>:
>> Whether support for gcc 2.95 should be dropped is a discussion for 2.7.
>
> Is there any single 3.x.x version of GCC that's actively in use by a large
> number of core developers? How do we make a sensible recommendation if not?
As an aside, it seems like gcc-3.3.3 is pretty good.
There are some known problems with it, but the number is small.
I haven't tried gcc-3.4.0 much yet, but I have seen a few kernel patches
to fix issues 3.4.0 found in the kernel source.
I agree 2.6 should continue to support and compile correctly under gcc-2.95.3,
even if that means working around compiler bugs. By the time linux-2.7
rolls around, I suspect nobody will mind if we drop 2.95.3 in favor
of 3.4.x. It'll be interesting to see if newer gccs optimize the kernel better...
- Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
next reply other threads:[~2004-05-29 15:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 14:42 Dan Kegel [this message]
2004-05-29 23:55 ` Recommended compiler version Karim Yaghmour
2004-05-29 23:20 ` Dan Kegel
2004-05-30 0:40 ` Karim Yaghmour
2004-05-30 0:38 ` Karim Yaghmour
2004-05-30 10:37 ` John Bradford
[not found] <218aB-15c-17@gated-at.bofh.it>
2004-05-29 10:51 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-05-29 9:16 Francois Romieu
2004-05-29 9:52 ` Francois Romieu
2004-05-29 13:30 ` John Bradford
2004-05-29 14:12 ` Francois Romieu
2004-05-29 14:31 ` Adrian Bunk
2004-05-29 14:57 ` John Bradford
2004-05-30 1:18 ` George Georgalis
2004-05-29 14:53 ` John Bradford
2004-05-29 16:58 ` Francois Romieu
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=40B8A161.5040306@kegel.com \
--to=dank@kegel.com \
--cc=john@grabjohn.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