Seth Mos wrote:
> How about running the code through the Stanford Vailidity Checker (SVC).
> It is build to seek out improper construct. It won't help you avoid
> compiler bugs but it will help you finding bad code in the tree. It won't
> fix them automatically.
I actually was talking with Dawson about this a while ago, and he seemed
interested. We still owe him comprehensive xfs-specific "rules" to
check, though, something that only a few people can probably put
together (steve, ananth... not me yet.).
I was hoping he'd run it through the standard kernel checks, but haven't
heard from him. I'll ping him again...
-Eric
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|