------- Comment #4 from gcc at brainhub dot org 2006-09-21 21:19 ------- I accepts Andrew's point, but note that you will get errors, not warnings, for identical C++ code.
The problem is exacerbate by libc prototypes such as size_t strlen(const char *s). If you want to use libc functions, perhaps for their efficient __built_in equivalents, all your strings will need to be char * strings or you need to use explicit casts. Most of code today is assuming unsigned char * strings; UTF-8 strings are unsigned char * strings, for example. Given this inconsistency it would be nice to have new option in gcc to suppress char-related signedness warnings. In many projects these warnings are just a noise. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28912
