On Fri, Aug 4, 2017 at 5:20 PM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: >> >> If it compress 20 seconds to 2 seconds. I vote for include it. > > If only it would do so for every input code ;) > Because the offending source is come from a system header file, I think it is more likely to hit in the field than average project source file. > > OK, considering also that the situation may be present in other > code (at various degree) and that this non-expansion of the > builtin is really bad I'm fine to include it. > > Strangely I have a series of 5 or 6 patches fixing some similar situations > (where some code is not evaluated and/or expanded, often creating > duplicated warnings) but not this precise case. > I never posted them because I considered it was too late in the release ... I already applied as patch to sparse-next. I am doing the kernel compile test right now. I will push it soon. I confirm it cut the offending compile from 23 secons to: real 0m3.425s user 0m3.237s sys 0m0.135s 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
