This is the mail archive of the gcc@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] |
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: cd gcc; make you miss uninitalised warnings and the like caught by: make all-gcc at the toplevel. Why shouldn't gcc's CFLAGS include -O2 given that most end-users are building using the toplevel Makefile? Cheers, Ben
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |