2013/7/3 Joseph S. Myers <jos...@codesourcery.com>: > On Wed, 3 Jul 2013, Graham Stott wrote: > >> Files in the c-family directory are being compiled during stage3 without >> -Werror and other warningb flags that are part of WARN_STRICT flags. >> Fixing this shows that array_notation_common.c generates unused >> variable warnings and will break the build after the apcth is applied. >> >> >> ChangeLog >> 03-07-2013 Graham Stott <graham.stott> >> * gcc/Makegfvile.in: Define c-family-warn. to WARN_STRICT. > > OK with a properly formatted ChangeLog entry, once the warnings are fixed > of course. > > 2013-07-03 Graham Stott <graham.st...@btinternet.com> > > * Makefile.in (c-family-warn): Define to $(WARN_STRICT). > > -- > Joseph S. Myers > jos...@codesourcery.com
Hi, Balaji, There is a warning in recent change of array_notation_common.c source. In the revision r200405: http://gcc.gnu.org/r200405 you made some changes in length_mismatch_in_expr_p() and use the variables l_length & l_node. But in the revision r200554: http://gcc.gnu.org/r200554 you removed following two statements: l_node = int_cst_value (list[ii][jj].length); l_length = int_cst_value (length); causing l_length & l_node to be unused variables. I think it is safe to remove the declaration to avoid warning after r200554. What do you think? :-) Best regards, jasonwucj