public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Randy Dunlap <randy.dunlap@oracle.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jarek Poplawski <jarkao2@o2.pl>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: RFC: drop support for gcc < 4.0
Date: Tue, 21 Aug 2007 20:29:32 +0200	[thread overview]
Message-ID: <20070821182932.GD30705@stusta.de> (raw)
In-Reply-To: <20070821175453.GB19819@flint.arm.linux.org.uk>

On Tue, Aug 21, 2007 at 06:54:53PM +0100, Russell King wrote:
> On Tue, Aug 21, 2007 at 07:35:50PM +0200, Adrian Bunk wrote:
> > On Tue, Aug 21, 2007 at 09:31:03AM -0700, Randy Dunlap wrote:
> > > On Tue, 21 Aug 2007 15:20:38 +0200 Jarek Poplawski wrote:
> > > 
> > > > Here are some more of, probably well-known, warnings with attached
> > > > testing-only .config.
> > > >...
> > > > drivers/pci/msi.c:686: warning: weak declaration of `arch_msi_check_device' after first use results in unspecified behavior
> > > > drivers/pci/msi.c:698: warning: weak declaration of `arch_setup_msi_irqs' after first use results in unspecified behavior
> > > > drivers/pci/msi.c:718: warning: weak declaration of `arch_teardown_msi_irqs' after first use results in unspecified behavior
> > > >...
> > > 
> > > What gcc version?  I don't get the arch_ warnings in drivers/pci/msi.c.
> > 
> > Obviously a gcc <= 3.4 [1], and therefore no unit-at-a-time.
> > 
> > You can reproduce it with a more recent gcc when adding 
> > -fno-unit-at-a-time to the CFLAGS.
> > 
> > And it's becoming a real maintainance problem that not only this problem 
> > but also other problems like some section mismatches [2] are only 
> > present without unit-at-a-time.
> > 
> > Currently we support 6 different stable gcc release series, and it might 
> > be the right time to consider dropping support for the older ones.
> > 
> > Are there any architectures still requiring a gcc < 4.0 ?
> 
> I want to keep support for gcc 3.4.3 for ARM for the forseeable future.
> >From my point of view, gcc 4 compilers have been something of a development
> thing as far as the ARM architecture goes.
>...

It is an option to say "gcc >= 4.0 on i386 and >= 3.4 on all other 
architectures is required".

> Russell King

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


  parent reply	other threads:[~2007-08-21 18:30 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 13:20 2.6.23-rc3-git3 make warnings Jarek Poplawski
2007-08-21 15:07 ` [Git Patch] ACPI: Fix a warning of discarding qualifiers from pointer target type WANG Cong
2007-08-21 15:14   ` Alexey Starikovskiy
2007-08-21 15:18     ` Al Viro
2007-08-21 15:22       ` Alexey Starikovskiy
2007-08-21 15:47         ` Al Viro
2007-08-23  0:59           ` Brown, Len
2007-08-23  1:28             ` Al Viro
2007-08-22  7:57       ` Jarek Poplawski
2007-08-21 16:17 ` 2.6.23-rc3-git3 make warnings WANG Cong
2007-08-21 16:44   ` Greg KH
2007-08-21 16:57     ` Adrian Bunk
2007-08-21 16:31 ` Randy Dunlap
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 [this message]
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
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=20070821182932.GD30705@stusta.de \
    --to=bunk@kernel.org \
    --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=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