public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: RFC: Raise required gcc version to 3.2 ?
Date: Fri, 29 Jul 2005 17:56:30 +0200	[thread overview]
Message-ID: <20050729155630.GF3563@stusta.de> (raw)
In-Reply-To: <200507281648.j6SGmnf0023871@harpo.it.uu.se>

On Thu, Jul 28, 2005 at 06:48:49PM +0200, Mikael Pettersson wrote:
> On Thu, 28 Jul 2005 14:00:12 +0200, Adrian Bunk wrote:
> >What is the oldest gcc we want to support in kernel 2.6?
> >
> >Currently, it's 2.95 .
> >
> >I'd suggest raising this to 3.2 which should AFAIK not be a problem for 
> >any distribution supporting kernel 2.6 .
> >
> >Is there any good reason why we should not drop support for older 
> >compilers?
> 
> You're asking the wrong question. The right question would be:
> "Is there any good reason to drop support for older compilers?"
> 
> At least on i386, gcc-2.95.3 still works and has the advantage
> of being much faster compile-time wise on older machines with
> limited memory (like my 486 test box). And I'm not the only
> one with that POV -- akpm also uses 2.95.
> 
> Of course, if keeping 2.95.3 support would somehow hinder the
> kernel's development, then it should be removed. But so far I
> haven't seen any real(*) evidence that this is the case.
>...

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.

> /Mikael

cu
Adrian

[1] support removed: 2.95, 2.96, 3.0, 3.1
    still supported: 3.2, 3.3, 3.4, 4.0

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-07-29 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 16:48 RFC: Raise required gcc version to 3.2 ? Mikael Pettersson
2005-07-29 15:56 ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-28 12:00 Adrian Bunk
2005-07-28 12:39 ` Krzysztof Halasa
2005-07-28 13:59   ` Lennart Sorensen
2005-07-28 17:05 ` Christoph Lameter

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=20050729155630.GF3563@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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