All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] janitor project: fix gcc 4 warnings
Date: Sun, 19 Dec 2004 20:03:24 +0000	[thread overview]
Message-ID: <20041219200324.GA44435@muc.de> (raw)
In-Reply-To: <20041219190903.GA30192@muc.de>

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

On Sun, Dec 19, 2004 at 07:47:59PM +0000, Matthew Wilcox wrote:
> On Sun, Dec 19, 2004 at 08:09:03PM +0100, Andi Kleen wrote:
> > Here's a proposed janitor project if anybody is interested:
> > 
> > The current gcc 4.0 snapshots include some more warnings in -Wall
> > and changed some existing ones which makes a kernel compilation quite noisy. 
> 
> I think it would get more takers if people didn't have to compile a new
> gcc.  If we had a list of -W... flags in older gccs that could simulate
> 90% of the warnings, this would make it possible for more people to work
> on it.

Problem is that some of the warnings are completely new in gcc 4 and
cannot be enabled with options in older versions. Also with a reasonable
modern machine (Athlon or P4) it won't take that long to do the gcc
compilation.

-Andi

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2004-12-19 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 19:09 [KJ] janitor project: fix gcc 4 warnings Andi Kleen
2004-12-19 19:47 ` Matthew Wilcox
2004-12-19 20:03 ` Andi Kleen [this message]
2004-12-19 21:00 ` Tobias Klauser
2004-12-20  0:13 ` Adrian Bunk
2004-12-20  7:10 ` Andi Kleen
2004-12-20  8:03 ` Andi Kleen
2004-12-20  8:04 ` Andi Kleen
2004-12-20 12:31 ` Arnd Bergmann
2004-12-22 16:44 ` Kovarththanan Rajaratnam
2005-02-07 23:14 ` Randy.Dunlap
2007-02-15 19:34 ` devzero

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=20041219200324.GA44435@muc.de \
    --to=ak@muc.de \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.