On 01/29/2014 12:49 PM, Paolo Carlini wrote:
By the way,
this recycling of TEMPLATE_TYPE_PARM + name seems weird to me too, I
noticed it a couple of times already (I think it shows in an open
diagnostic issue too). I think the alternative would an additional
TREE_CODE and a lot of uses of it wher
On 01/29/2014 06:41 PM, Cary Coutant wrote:
in this bug we ICE in dwarf2out.c:is_base_type with -g, because it doesn't
know how to handle the TEMPLATE_TYPE_PARM coming from the C++ front-end and
representing 'auto' in this kind of C++1y code.
That it shouldn't ICE and return 0 instead I'm pretty
> in this bug we ICE in dwarf2out.c:is_base_type with -g, because it doesn't
> know how to handle the TEMPLATE_TYPE_PARM coming from the C++ front-end and
> representing 'auto' in this kind of C++1y code.
>
> That it shouldn't ICE and return 0 instead I'm pretty sure, I'm less sure
> about the next
Hi,
in this bug we ICE in dwarf2out.c:is_base_type with -g, because it
doesn't know how to handle the TEMPLATE_TYPE_PARM coming from the C++
front-end and representing 'auto' in this kind of C++1y code.
That it shouldn't ICE and return 0 instead I'm pretty sure, I'm less
sure about the next
