On Tuesday 11 of August 2009 23:08:24 Christopher Li wrote: > On Tue, Aug 11, 2009 at 3:40 AM, Kamil Dudka<kdudka@xxxxxxxxxx> wrote: > > I agree processing of multiple-includes could be painful for the SPARSE > > preprocessor. But you don't solve it by avoiding multiple-includes in the > > SPARSE code itself. If you want to pass the SPARSE code through SPARSE, > > it's small enough to not bother us with performance. > > I am worry about adding too much duplicated include slow down the > gcc compile of sparse itself. I know I am paranoid :-) Tested just now (ccache turned off)... With the original (not amended) patch: $ make clean && time make -j9 real 0m0.966s user 0m4.654s sys 0m1.471s With the amended patch: $ make clean && time make -j9 real 0m0.989s user 0m4.580s sys 0m1.504s Without any of my patches applied: $ make clean && time make -j9 real 0m0.980s user 0m4.596s sys 0m1.495s Note that the results fluctuated approx 10% during runs. My conclusion: absolutely no impact on gcc compile time. Kamil -- 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
