On Wed, 7 Sep 2005, Mitesh Shah wrote:
>
> Is there a way to distinguish between the warnings and the errors? I see
> that sparse is trying to continue even if it encounters an error (error in
> gcc sense). For example, missing semicolon is printed as a warning. Is there
> a way to print such things (that treated as errors by gcc) as errors?
I think we should make "error()" just die. Continuing was fine back in the
old days when we had tons of bogus errors, but there's little point to it
any more, I suspect.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
