linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jarek Poplawski <jarkao2@o2.pl>, Andi Kleen <ak@suse.de>,
	linux-arch@vger.kernel.org,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: RFC: drop support for gcc < 4.0
Date: Tue, 21 Aug 2007 23:21:29 +0200	[thread overview]
Message-ID: <20070821212129.GG30705@stusta.de> (raw)
In-Reply-To: <27c412eea99f1f80a3002e9668bd31f8@kernel.crashing.org>

On Tue, Aug 21, 2007 at 10:49:49PM +0200, Segher Boessenkool wrote:
>> How many people e.g. test -rc kernels compiled with gcc 3.2?
>
> Why would that matter?  It either works or not.  If it doesn't
> work, it can either be fixed, or support for that old compiler
> version can be removed.

One bug report "kernel doesn't work / crash / ... when compiled with
gcc 3.2, but works when compiled with gcc 4.2" will most likely be lost 
in the big pile of unhandled bugs, not cause the removal of gcc 3.2 
support...

> The only other policy than "only remove support if things are
> badly broken" would be "only support what the GCC team supports",
> which would be >= 4.1 now; and there are very good arguments for
> supporting more than that with the Linux kernel.

No, it's not about bugs in gcc, it's about kernel+gcc combinations that 
are mostly untested but officially supported.

E.g. how many kernel developers use kernels compiled without 
unit-at-a-time? And unit-at-a-time does paper over some bugs,
e.g. at about half a dozen section mismatch bugs I've fixed
recently are not present with it.

But as the discussions have shown gcc 4.0 is currently too high for 
making a cut, and it is not yet the right time for raising the minimum 
required gcc version.

> Segher

cu
Adrian

-- 

       "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:[~2007-08-21 21:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070821132038.GA22254@ff.dom.local>
     [not found] ` <20070821093103.3c097d4a.randy.dunlap@oracle.com>
2007-08-21 17:35   ` RFC: drop support for gcc < 4.0 Adrian Bunk
2007-08-21 17:54     ` Russell King
2007-08-21 18:14       ` Kyle McMartin
2007-08-21 18:29       ` Adrian Bunk
2007-08-22  5:48         ` Robert P. J. Day
2007-08-21 18:25     ` Chris Wedgwood
2007-08-21 20:41       ` Glauber de Oliveira Costa
2007-08-21 20:56         ` Segher Boessenkool
2007-08-21 21:01           ` Glauber de Oliveira Costa
2007-08-22  6:59         ` Thomas Bogendoerfer
2007-08-22 18:15         ` Ralf Baechle
2007-08-21 19:19     ` Andi Kleen
2007-08-21 19:54       ` Adrian Bunk
2007-08-21 20:07         ` [RFC][PATCH] introduce TASK_SIZE_OF() for all arches Matthew Wilcox
2007-08-21 20:08         ` RFC: drop support for gcc < 4.0 Linus Torvalds
2007-08-21 20:21           ` Adrian Bunk
2007-08-21 20:32             ` Linus Torvalds
2007-08-22  7:36               ` Jarek Poplawski
2007-08-21 20:49             ` Segher Boessenkool
2007-08-21 21:21               ` Adrian Bunk [this message]
2007-08-21 21:49                 ` James Bottomley
2007-08-21 22:09                   ` Adrian Bunk
2007-08-22  0:08                 ` Segher Boessenkool
2007-08-22  6:07                   ` Jarek Poplawski
2007-08-21 21:41     ` Oliver Pinter
2007-08-22  7:57       ` Jan Engelhardt
2007-08-22  8:08         ` Jarek Poplawski
2007-08-22  8:10           ` Jan Engelhardt
2007-08-22  8:42             ` Michal Piotrowski
2007-08-22  8:56             ` Jarek Poplawski
2007-08-22  8:48         ` Martin Michlmayr

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=20070821212129.GG30705@stusta.de \
    --to=bunk@kernel.org \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=jarkao2@o2.pl \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=segher@kernel.crashing.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).