]> git.kernelconcepts.de Git - karo-tx-linux.git/commit
gcov: disable -Wmaybe-uninitialized warning
authorArnd Bergmann <arnd@arndb.de>
Mon, 25 Apr 2016 15:35:31 +0000 (17:35 +0200)
committerMichal Marek <mmarek@suse.com>
Tue, 10 May 2016 15:12:50 +0000 (17:12 +0200)
commite72e2dfe7c16ffbfbabf9cb24adc6d9f93a4fe37
tree5b7d4cf20cf35b6b3ae036f603ee71e81d313e12
parentc87bf431448b404a6ef5fbabd74c0e3e42157a7f
gcov: disable -Wmaybe-uninitialized warning

When gcov profiling is enabled, we see a lot of spurious warnings about
possibly uninitialized variables being used:

arch/arm/mm/dma-mapping.c: In function 'arm_coherent_iommu_map_page':
arch/arm/mm/dma-mapping.c:1085:16: warning: 'start' may be used uninitialized in this function [-Wmaybe-uninitialized]
drivers/clk/st/clk-flexgen.c: In function 'st_of_flexgen_setup':
drivers/clk/st/clk-flexgen.c:323:9: warning: 'num_parents' may be used uninitialized in this function [-Wmaybe-uninitialized]
kernel/cgroup.c: In function 'cgroup_mount':
kernel/cgroup.c:2119:11: warning: 'root' may be used uninitialized in this function [-Wmaybe-uninitialized]

All of these are false positives, so it seems better to just disable
the warnings whenever GCOV is enabled. Most users don't enable GCOV,
and based on a prior patch, it is now also disabled for 'allmodconfig'
builds, so there should be no downsides of doing this.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
Signed-off-by: Michal Marek <mmarek@suse.com>
Makefile