[Bug build/9523] build error in incall.c on gcc 3.2.3, due to compiler warning with -Werror

["robert dot bu at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From robert dot bu at gmail dot com  2009-01-22 01:26 -------
Subject: Re:  build error in incall.c on gcc 3.2.3, due to 
	compiler warning with -Werror

Yes. It can be a gcc-3.2.3 -O2 bug. Without -O2, it compiles without any
problem. I tried gcc-3.3.6 here, and didn't encounter the problem.

Thank you for your kind patience.

-----Original Message-----
From: pedro at codesourcery dot com
Sent: 2009-01-21 21:39

> ------- Additional Comments From pedro at codesourcery dot com  2009-01-21 13:38 -------
> Ok, thanks.  That's a different warning though:
>
> old:
>> ../../gdb/gdb/infcall.c: In function `find_function_addr':
>> ../../gdb/gdb/infcall.c:197: warning: initialization makes integer from pointer
>> make[2]: *** [infcall.o] Error 1
>
> new:
> ./../src/gdb/infcall.c: In function `find_function_addr':
> ./../src/gdb/infcall.c:212: warning: `funaddr' might be used
> uninitialized in this function
>
> I can't see any path where funaddr might be used uninitialized, though.
> Maybe a gcc-3.2.3 bug?  I happen to have gcc 3.3 and 3.4 on my box, and
> those also don't trigger this.
>
> Initializing to NULL may silently hide some future bugs, where that
> warning would be useful.  Oh, well, we should handle this somehow.
>
>


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9523

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.