Hello, > Another approach I'd be comfortable with would be to perform a second pass > looking for a string match if the pointer match fails, and to emit a > differently-worded message in that case (explaining that the problem might be > due to an RTLD_LOCAL library, or using hidden visibility for the type, or > linking against code produced by a compiler that violates the ABI).
+1. Isn't the case of two different type_info objects for the same type a violation of ODR anyway (i.e. wouldn't this be something the UB sanitizer should check for)? Jonathan _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
