Description of problem:

We cannot figure out whether GCC thinks C should use DW_ATE_{un,}signed_char or
DW_ATE_{un,}signed for the "char" types.  From the source code it looks like the
*_char types (CHAR_TYPE) are not used in C.  But in practice it sometimes
generates one and sometimes the other.


Version-Release number of selected component (if applicable):
gcc-4.0.1-4.fc4

How reproducible:


Steps to Reproduce:
1.echo "char a = 'x'; const char b = 'x';" | gcc -g -o char.o -c -x c - ;
eu-readelf --debug-dump=info char.o
2.echo "const char a = 'x'; char b = 'x';" | gcc -g -o char.o -c -x c - ;
eu-readelf --debug-dump=info char.o
3. Compare the base_type with name "char" in each.
  
Actual results:

One says "encoding             signed_char (6)".
One says "encoding             signed (5)".

Expected results:

Consistent definition of DWARF encoding for base types.

Additional info: