On 06/12/2014 03:14 PM, Paolo Carlini wrote:
... in terms of code proper, the below is much better, IMHO. Assuming, as I understand, we have no reason to call the rather heavy same_type_p when we already know that VOID_TYPE_P (type) is true...
same_type_p is not so heavy since it just compares TYPE_CANONICAL, but I wonder why we don't use == for the normal case, and then typedef_variant_p to diagnose a typedef.
Jason