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

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


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. 

The project would be to fix all these warnings.

Short howto: 

Get
ftp://gcc.gnu.org/pub/gcc/snapshots/4.0-20041219/gcc-core-4.0-20041219.tar.bz2

Untar it and compile with 

mkdir obj
../gcc-*/configure --disable-checking --enable-languages=c --prefix=/usr/local/gcc4
make bootstrap
<as root> 
make install


Then compile an uptodate 2.6 kernel with:

make allmodconfig
make CC=/usr/local/gcc4/bin/gcc 2>&1 | tee LOG
grep warning LOG 

You'll see lots of warnings in LOG. Fix them all and submit patches
through the usual janitor channels.

-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

             reply	other threads:[~2004-12-19 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 19:09 Andi Kleen [this message]
2004-12-19 19:47 ` [KJ] janitor project: fix gcc 4 warnings Matthew Wilcox
2004-12-19 20:03 ` Andi Kleen
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=20041219190903.GA30192@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.