Skip to content

Commit e74fc97

Browse files
committed
Turn off -Wmaybe-uninitialized when building with -Os
gcc-4.7 and higher add a lot of false positive warnings about potential uses of uninitialized warnings, but only when optimizing for size (-Os). This is the default when building allyesconfig, which turns on CONFIG_CC_OPTIMIZE_FOR_SIZE. In order to avoid getting a lot of patches that initialize such variables and accidentally hide real errors along the way, let's just turn off this warning on the respective gcc versions when building with size optimizations. The -Wmaybe-uninitialized option was introduced in the same gcc version (4.7) that is now causing the false positives, so there is no effect on older compilers. A side effect is that when building with CONFIG_CC_OPTIMIZE_FOR_SIZE, we might now see /fewer/ warnings about possibly uninitialized warnings than with -O2, but that is still much better than seeing warnings known to be bogus. Signed-off-by: Arnd Bergmann <arnd@arndb.de>
1 parent 7b2fea1 commit e74fc97

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -570,7 +570,7 @@ endif # $(dot-config)
570570
all: vmlinux
571571

572572
ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
573-
KBUILD_CFLAGS += -Os
573+
KBUILD_CFLAGS += -Os $(call cc-disable-warning,maybe-uninitialized,)
574574
else
575575
KBUILD_CFLAGS += -O2
576576
endif

0 commit comments

Comments
 (0)