Skip to contentSkip to conversation

janitor project: fix gcc 4 warnings

KJ Domen Puncer 1 participant 1 message Dec 20, 2004 Kernel janitors

lore
Share & tools
lore
#0 lore raw
Quoted 18 lines · Tobias Klauser

Hi

Quoted 15 lines · Andi Kleen

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

Quoted 7 lines
Quoted 5 lines

Then compile an uptodate 2.6 kernel with:

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

Cool howto, thanks. Maybe that should go onto the TODO list over at kerneljanitors.org?

Added.

Quoted 11 lines
Quoted 4 lines

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

I already compiled GCC4 and it took about 15 minutes on an Athlon Tbird 1.4 GHz to finish. When compiling Linux 2.6.10-rc3 with GCC4 there are lots of warnings (as expected) and even a fatal error.
So I'm trying to fix some of these warnings. They are all over the kernel tree and so I'm curious what would be the best method to split and submit the patches?

Patch per file (and per mail).
For submitting, Andrew's patch-bomb (from patch-scripts) might be useful.

Domen

_______________________________________________
Kernel-janitors mailing list
[email protected]
http://lists.osdl.org/mailman/listinfo/kernel-janitors