C/C++ FEs: Do we really need three char_type_nodes?

[Paolo Bonzini]

Diego Novillo wrote:
> On Fri, Sep 19, 2008 at 12:55, Jakub Jelinek <jakub@redhat.com> wrote:
>> On Fri, Sep 19, 2008 at 12:36:12PM -0400, Diego Novillo wrote:
>>> When we instantiate char_type_node in tree.c:build_common_tree_nodes
>>> we very explicitly create a char_type_node that is signed or unsigned
>>> based on the value of -funsigned-char, but instead of make
>>> char_type_node point to signed_char_type_node or
>>> unsigned_char_type_node, we explicitly instantiate a different type.
>> C++ e.g. requires that char (c) is mangled differently from unsigned char
>> (h) and signed char (a), it is a distinct type.
> 
> Thanks, that answer my question.

But does it need to be streamed out differently?  I mean, char_type_node
could be streamed out as signed_char_type_node or
unsigned_char_type_node, because the mangling has already been done.

Paolo