Some GDB files won't compile with GCC 4.1, when -Werror is used

Some GDB files won't compile with GCC 4.1, when -Werror is used

[Maxim Grigoriev]

Hello everyone,

My codeline is synchronized with the main GDB CVS sources.
Am I the only individual who's unable to compile .../gdb/p-valprint.c 
and .../gdb/cp-valprint.c with GCC 4.1 ?
Host is i686-pc-linux-gnu.

 >>>>> uname -a
Linux .... 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006 i686 i686 
i386 GNU/Linux

 >>>>> gcc --version
gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)
Copyright (C) 2006 Free Software Foundation, Inc.
...............

Then, an extraction from the logfile :
gcc -c -g -O2    -I. -I/home/maxim/G/BadgerPass/GDB/CVS/src/gdb 
-I/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/config 
-DLOCALEDIR="\"/home/maxim/W/GDBsubmit/share/locale\"" -DHAVE_CONFIG_H 
-I/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/../include/opcode 
-I/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/../readline/.. -I../bfd 
-I/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/../bfd 
-I/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/../include   -DMI_OUT=1 
-DTUI=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat 
-Wparentheses -Wpointer-arith -Wformat-nonliteral -Wunused-label 
-Wunused-function -Wno-pointer-sign -Wuninitialized -Werror 
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c
cc1: warnings being treated as errors
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c: In function 
'pascal_object_print_value_field':
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.alloc_failed' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.maybe_empty_object' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.use_extra_arg' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.extra_arg' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.freefun' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.chunkfun' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.alignment_mask' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.temp' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.chunk_limit' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.next_free' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.object_base' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.chunk' may be used uninitialized in this function
/home/maxim/G/BadgerPass/GDB/CVS/src/gdb/p-valprint.c:756: warning: 
'tmp_obstack.chunk_size' may be used uninitialized in this function
make[2]: *** [p-valprint.o] Error 1
make[2]: Leaving directory `.../gdb'
make[1]: *** [all-gdb] Error 2

Thanks,
-- Maxim

Re: Some GDB files won't compile with GCC 4.1, when -Werror is used

[Daniel Jacobowitz]

On Mon, Jul 24, 2006 at 05:41:08PM -0700, Maxim Grigoriev wrote:
> Hello everyone,
> 
> My codeline is synchronized with the main GDB CVS sources.
> Am I the only individual who's unable to compile .../gdb/p-valprint.c 
> and .../gdb/cp-valprint.c with GCC 4.1 ?
> Host is i686-pc-linux-gnu.
> 
> >>>>> uname -a
> Linux .... 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006 i686 i686 
> i386 GNU/Linux
> 
> >>>>> gcc --version
> gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)
> Copyright (C) 2006 Free Software Foundation, Inc.

I don't get this problem with gcc 4.1.2.  I don't know which version of
GCC is more correct.


-- 
Daniel Jacobowitz
CodeSourcery

Re: Some GDB files won't compile with GCC 4.1, when -Werror is used

[Maxim Grigoriev]

>> I don't get this problem with gcc 4.1.2.  I don't know which version of
>> GCC is more correct.

The source code looks fine to me. So it seems to be a "Red Hat 
4.1.0-3"-specific (mis)behavior.

-- Maxim

Daniel Jacobowitz wrote:
> On Mon, Jul 24, 2006 at 05:41:08PM -0700, Maxim Grigoriev wrote:
>   
>> Hello everyone,
>>
>> My codeline is synchronized with the main GDB CVS sources.
>> Am I the only individual who's unable to compile .../gdb/p-valprint.c 
>> and .../gdb/cp-valprint.c with GCC 4.1 ?
>> Host is i686-pc-linux-gnu.
>>
>>     
>>>>>>> uname -a
>>>>>>>               
>> Linux .... 2.6.15-1.2054_FC5 #1 Tue Mar 14 15:48:33 EST 2006 i686 i686 
>> i386 GNU/Linux
>>
>>     
>>>>>>> gcc --version
>>>>>>>               
>> gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)
>> Copyright (C) 2006 Free Software Foundation, Inc.
>>     
>
> I don't get this problem with gcc 4.1.2.  I don't know which version of
> GCC is more correct.
>
>
>