On Sun, 1 Oct 2006, Al Viro wrote: > > PS: "fouled(le16)" is exactly "int, and if you narrow it to 16bit, it'd > better be le16". We could separate that from type information, but hey, > if we want to carry reference to some type + indication that we do have > that reference + int as type, we might as well introduce a type node > saying "I'm int, might be base_type". Which is exactly what I've done... Ok, I'm convinced. The "fouled" bit may be a special case, but it's less of a special case than I thought. In fact, it could be used as a preliminary kind of "expand this op to int" that would entirely replace the explicit "implicit cast" we do now. (Although doing the implicit C casts as _explicit_ casts in sparse does have a lot of advantages, and avoids us having to test for things, so I'm not convinced we would want to actually expand "fouled" bit usage past the bitwise ops). So I'll pull your tree. Thanks, Linus - 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
