From: Willy Tarreau <willy@w.ods.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove support for gcc < 3.2
Date: Tue, 2 Aug 2005 07:37:39 +0200 [thread overview]
Message-ID: <20050802053739.GA20363@alpha.home.local> (raw)
In-Reply-To: <20050801030145.GE20899@kurtwerks.com>
On Sun, Jul 31, 2005 at 11:01:45PM -0400, Kurt Wall wrote:
> On Mon, Aug 01, 2005 at 12:26:07AM +0200, Adrian Bunk took 109 lines to write:
> > This patch removes support for gcc < 3.2 .
> >
> > The advantages are:
> > - reducing the number of supported gcc versions from 8 to 4 [1]
> > allows the removal of several #ifdef's and workarounds
> > - my impression is that the older compilers are only rarely
> > used, so miscompilations of a driver with an old gcc might
> > not be detected for a longer amount of time
> >
> > My personal opinion about the time and space a compilation requires is
> > that this is no longer that much of a problem for modern hardware, and
> > in the worst case you can compile the kernels for older machines on more
> > recent machines.
>
> Environments that require kernel compilation, often multiple times,
> testing, benefit from shorter compile times. It can be the difference
> between, say, completing a test suite overnight instead of having to
> wait until tomorrow afternoon. Keeping 2.95, at least, has some value
> in such environments.
I *do* still use 2.95 a lot, and I'm not alone, judging from people
around me. 2.95 has been the reference for a very long time, that's
why it's still so much present. 3.0 and 3.1 (even 3.2) have been
there for a very short time frame, but 2.95 and 3.3 really seem to
be references compilers.
So please keep support for 2.95.
Cheers,
Willy
next prev parent reply other threads:[~2005-08-02 5:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 22:26 Adrian Bunk
2005-07-31 22:36 ` David S. Miller
2005-07-31 23:08 ` Nigel Cunningham
2005-08-07 16:25 ` Denis Vlasenko
2005-08-10 19:40 ` Bill Davidsen
2005-08-11 0:02 ` Joe
2005-08-11 0:05 ` David S. Miller
2005-08-13 3:27 ` Bill Davidsen
2005-08-01 3:01 ` [2.6 patch] " Kurt Wall
2005-08-02 5:37 ` Willy Tarreau [this message]
2005-08-01 4:27 ` Miles Bader
2005-08-02 21:46 ` Jan-Benedict Glaw
2005-08-03 2:08 ` Gustavo Guillermo Pérez
2005-08-04 0:53 ` Mathieu Chouquet-Stringer
2005-08-04 20:34 ` networking problems when using gcc 4.0.1 Adrian Bunk
2005-08-04 1:34 ` [2.6 patch] remove support for gcc < 3.2 Dave Airlie
2005-08-04 6:54 ` Jan-Benedict Glaw
2005-08-04 20:38 ` Adrian Bunk
2005-08-05 21:14 ` Jan-Benedict Glaw
2005-08-05 21:30 ` Martin Drab
2005-08-05 21:37 ` Jan-Benedict Glaw
2005-08-13 9:21 ` Jan-Benedict Glaw
2005-08-12 7:40 ` Geert Uytterhoeven
2005-08-12 10:40 ` Maciej W. Rozycki
2005-08-12 12:29 ` Jan-Benedict Glaw
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=20050802053739.GA20363@alpha.home.local \
--to=willy@w.ods.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
all inboxes | Powered by JetHome®