2009/12/21 Sam Ravnborg <sam@xxxxxxxxxxxx>: > On Sun, Dec 20, 2009 at 03:16:35PM +0300, Alexander Beregalov wrote: >> Fix warnings which become build errors since -Werror is used. >> arch/sparc/kernel/us3_cpufreq.c:60: error: 'ret' may be used uninitialized in this function >> arch/sparc/kernel/us3_cpufreq.c:101: error: 'new_bits' may be used uninitialized in this function > > What config produces these warnings? > Do you have CONFIG_BUG_VERBOSE set? > > Also what gcc versio? > Hi I do not know what has changed. I have not tried these options before. I tested randconfig builds. Config is attached. gcc is 4.3.4 sparc64-unknown-linux-gnu-gcc -Wp,-MD,arch/sparc/kernel/.us3_cpufreq.o.d -nostdinc -isystem /usr/lib/gcc/sparc64-unknown-linux-gnu/4.3.4/include -I/home/alexb/src/linux-2.6/arch/sparc/include -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -Os -m64 -pipe -mno-fpu -mcpu=ultrasparc -mcmodel=medlow -ffixed-g4 -ffixed-g5 -fcall-used-g7 -Wno-sign-compare -Wa,--undeclared-regs -mtune=ultrasparc3 -pg -fno-stack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -Werror -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(us3_cpufreq)" -D"KBUILD_MODNAME=KBUILD_STR(us3_cpufreq)" -D"DEBUG_HASH=11" -D"DEBUG_HASH2=39" -c -o arch/sparc/kernel/.tmp_us3_cpufreq.o arch/sparc/kernel/us3_cpufreq.c cc1: warnings being treated as errors arch/sparc/kernel/us3_cpufreq.c: In function 'get_current_freq': arch/sparc/kernel/us3_cpufreq.c:60: error: 'ret' may be used uninitialized in this function arch/sparc/kernel/us3_cpufreq.c: In function 'us3_set_cpu_divider_index': arch/sparc/kernel/us3_cpufreq.c:101: error: 'new_bits' may be used uninitialized in this function make[1]: *** [arch/sparc/kernel/us3_cpufreq.o] Error 1
Attachment:
config-sparc-rand
Description: Binary data
