On Sat, Aug 12, 2017 at 10:22 AM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > uh no. > It's exactly how it's already working now. > But it's exactly what is the problem when something > silly, caused by an internal bug, change at *each* > cycle and this it's what this patch avoid. If there is change at each cycle then the change flag will not help. I haven't seen those dead loop so I did not know what is the nature of those. I assume there is also other kind of deadloop if we think there is some thing can CSE but no actual change to the CFG. > > Of course, there is plenty of ways to do the same > or something similar or something which will have > the same result. This patch is just a very simple, > no non-sense way to do it. > Sure. It is simple enough. 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
