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 :-) > > But you have absolutely no control of the foreign code processed by SPARSE > and there the performance impact could be significant. I think this is the > way to go: > > http://gcc.gnu.org/onlinedocs/cppinternals/Guard-Macros.html BTW, sparse does similar things already. That is what the stream->protect was for. 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
