On Wed, Jul 19, 2017 at 2:14 PM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > When I see this description, the first thing I think is: > "you have a problem with an object, you duplicate the object, > not you have two problem (at least)". > In short, how you will keep coherency between the two? We don't :-). Both the remove case and insert case has been discussed. First of all, the ptrlist-refcount patch check for the insert case, there is none so far. If you believe there is one, I would like to know. About the looping on the deleted entry. That is the very first thing I shout in the V1 version of the patch. The thing is, the pseudo_user have a point to instruction. If the instruction is deleted then that instruction will have insn->bb = NULL. Not a perfect fix. But better than the previous. Because the for loop is actually looping on reverse order. Any delete will cause major align problem __nr counting from the tail. Any way, My V1 and email asking for suggestion how to fix it About 10 days ago. I haven't heard any thing better. If you have other way to fix it properly, I am all for it. It is not too late but time is running out soon. Chris -- 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
