On Mon, Feb 01, 2016 at 03:47:16AM +0100, Nicolai Stange wrote: > The expression parsing code builds an EXPR_COMPARE expression around two > EXPR_TYPE expressions for __builtin_types_compatible_p(). > > The EXPR_TYPE expressions are tagged as being integer constant expressions > in order to trick the generic comparison evaluation code into flagging the > result as an integer constant expression again. > > Avoid this trickery by making evaluate_compare() unconditionally tag a > comparsion between types as an integer constant expression. Fine for me. Feel free to add Reviewed-by: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
