This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: m68k bootstrapping broken


On Thu, Jan 15, 2004 at 12:57:47AM +0100, Bernardo Innocenti wrote:


> stage2/xgcc -Bstage2/ 
> -B/home/bernie/src/m68k-netbsdelf-HEAD-install/m68k-unknown-netbsdelf1.6.2./bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition -fno-common   -DHAVE_CONFIG_H    -I. -I. -I../../combined-HEAD/gcc -I../../combined-HEAD/gcc/. -I../../combined-HEAD/gcc/../include  ../../combined-HEAD/gcc/bb-reorder.c -o bb-reorder.o
> ../../combined-HEAD/gcc/bb-reorder.c: In function `reorder_basic_blocks':
> ../../combined-HEAD/gcc/bb-reorder.c:186: warning: 'count_threshold' might 
> be used uninitialized in this function
> 
> 
> Could you please try running this exact command line on your system to
> make absolutely sure it's only happening on m68k-netbsdelf?
> 

the line has several m68k-netbsd strings in it. Here is what I see:

stage2/xgcc -Bstage2/ -B/usr/m68k-rz-linux/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition -Werror    -DHAVE_CONFIG_H    -I. -I. -I../../gcc-3.4-20040107/gcc -I../../gcc-3.4-20040107/gcc/. -I../../gcc-3.4-20040107/gcc/../include  ../../gcc-3.4-20040107/gcc/bb-reorder.c -o bb-reorder.o
## no warnings

Anyway - is it at all reasonable to have -Werror quit on "might be used
uninitialized" warnings? It is really very dependent on gcc version and
possibly other circumstances so it makes -Werror probably less usefull
than it could be.

Richard


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]