Re: inconsistent CFLAGS between toplevel and gcc/

2005-07-17 Thread Ben Elliston
> "make bootstrap" should have caught the warnings. It did not. Here's an example: (compiles cleanly) [EMAIL PROTECTED]:~/build/gcc-mainline/gcc$ stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -p

Re: inconsistent CFLAGS between toplevel and gcc/

2005-07-17 Thread Andrew Pinski
On Jul 18, 2005, at 12:32 AM, Ben Elliston wrote: I have recently been noticing inconsistent warnings when building GCC (for example, warnings about uninitialised variables in gcc/ddg.c). I had not realised it, but the top-level CFLAGS defaults to "-g -O2" whereas gcc's Makefile sets CFLAGS

inconsistent CFLAGS between toplevel and gcc/

2005-07-17 Thread Ben Elliston
I have recently been noticing inconsistent warnings when building GCC (for example, warnings about uninitialised variables in gcc/ddg.c). I had not realised it, but the top-level CFLAGS defaults to "-g -O2" whereas gcc's Makefile sets CFLAGS to "-g" by default. So, if you compile this way: