Al Viro wrote:
g++ won't cover all checks sparse is capable of, so you still want to
run the latter over new code anyway (== pass C=1 to make). IOW, type
safety from C++ isn't particulary good argument.
I'm pretty sure that sparse can't validate all the casting from void
pointers and from "base classes". Nor can it find bugs in data
structures which are open-coded instead of template libraries. Do
correct me if I'm wrong.
I'm not familiar with sparse's capabilities beyond __user, locking
depth, and the like (pulling it now). Can you point me to any information?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
