Use -Wno-pointer-sign for gcc 4.0
diff mbox series

Message ID 20050119045552.GA77900@muc.de
State New, archived
Headers show
Series
  • Use -Wno-pointer-sign for gcc 4.0
Related show

Commit Message

Andi Kleen Jan. 19, 2005, 4:55 a.m. UTC
Compiling an allyesconfig kernel straight with a gcc 4.0 snapshot
gives nearly 10k new warnings like:

warning: pointer targets in passing argument 5 of `cpuid' differ in signedness

Since the sheer number of these warnings was too much even for the 
most determined kernel janitors (I actually asked ;-) and I don't
think it's a very serious issue to have these mismatches I submitted
an new option to gcc to disable it. It was incorporated in gcc mainline
now. 

This patch makes the kernel compilation use it. There are still
quite a lot of new warnings with 4.0 (mostly about uninitialized variables),
but the compile log looks much nicer nnow.

Signed-off-by: Andi Kleen <ak@suse.de>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Patch
diff mbox series

--- linux-2.6.11-rc1-bk4/Makefile-o	2005-01-17 10:39:39.000000000 +0100
+++ linux-2.6.11-rc1-bk4/Makefile	2005-01-19 05:43:29.000000000 +0100
@@ -533,6 +533,9 @@ 
 # warn about C99 declaration after statement
 CFLAGS += $(call cc-option,-Wdeclaration-after-statement,)
 
+# disable pointer signedness warnings in gcc 4.0
+CFLAGS += $(call cc-option,-Wno-pointer-sign,)
+
 # Default kernel image to build when no specific target is given.
 # KBUILD_IMAGE may be overruled on the commandline or
 # set in the environment