On Thu, Mar 22, 2007 at 12:59:11PM +0000, Al Viro wrote: > On Thu, Mar 22, 2007 at 12:03:54AM -0700, Christopher Li wrote: > Humm... I don't see ppc segfaults with the current tree. However, after > merging the mainline sparse changes and looking for regressions on kernel > allmodconfig builds, I'm seeing a lot of noise due to expression_error() use. > What used to generate a single error now brings a cascade. More often than Can you show me some example of the duplicate error? I can't seem to hit it in on x86. I do notice though there is a few context imbalance report on the inline function instead of the caller site. > not it's utterly pointless; actually, I can't find a single instance where > additional errors would add any useful information... The expression_error is not intend to report more error. It is try to avoid test expr->ctype against zero all the time. We often have error path there is some expression has NULL in ctype then sparse segfaulted. We can work on clean up the duplicate warnings. 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
