m3-sys/m3cc/gcc-4.5/gcc/c-common.c
/* Subscripting with type char is likely to lose on a machine where
   chars are signed.  So warn on any machine, but optionally.  Don't
   warn for unsigned char since that type is safe.  Don't warn for
   signed char because anyone who uses that must have done so
   deliberately. Furthermore, we reduce the false positive load by
   warning only for non-constant value of type char.  */
Subscripting with type char is likely to lose on a machine where
chars are signed.  So warn on any machine, but optionally.  Don't
warn for unsigned char since that type is safe.  Don't warn for
signed char because anyone who uses that must have done so
deliberately. Furthermore, we reduce the false positive load by
warning only for non-constant value of type char.
Subscripting with type char is likely to lose on a machine where chars are signed . So warn on any machine but optionally . Don ' t warn for unsigned char since that type is safe . Don ' t warn for signed char because anyone who uses that must have done so deliberately . Furthermore we reduce the false positive load by warning only for non - constant value of type char .
void
warn_array_subscript_with_type_char (tree index)
{
  if (TYPE_MAIN_VARIANT (TREE_TYPE (index)) == char_type_node
      && TREE_CODE (index) != INTEGER_CST)
    warning (OPT_Wchar_subscripts, "array subscript has type %<char%>");
}
void warn_array_subscript_with_type_char ( tree index ) { if ( TYPE_MAIN_VARIANT ( TREE_TYPE ( index ) ) == char_type_node && TREE_CODE ( index ) != INTEGER_CST ) warning ( OPT_Wchar_subscripts , " " ) ; }
Subscripting with type char is likely to lose on a machine where
chars are signed.
Subscripting with type char is likely to lose on a machine where chars are signed .