On Wed, Nov 23, 2016 at 12:44:36AM +0800, Christopher Li wrote: > > It is private to the back end. If you consider test-linearize as one of > the back end, it compile the C code into readable text form. it is fine > to use it. I assume the label ID is only make sense for test-linearize, > not for other back end? I use it for test-linearize, test-unssa and others stuff I'll coming up with in the coming weeks I hope. So nothing I consider as 'private', external or out-of-tree. > I am also OK with just introduce one more field ID for basic blocks. > There are far less basic blocks than instructions. So even size of basic > block bump up by a integer is not a big deal. Yes, I think so too. But anyway, I already sent a patch which reuse the 'priv' member with an union. It will always be very easy to remove the union later if needed. > > Sure. > > But it should be noted that this filtering stuff *could* be useful for other > > things to (but I have no such uses). > > We can always deal with it when such usage actually come up. Absolutely. Luc -- 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
