| commit | c9a0929d3deaf39ea5822bce90e126706bf5ead4 | |
| author | Dan Carpenter <error27@gmail.com> | |
| Tue, 27 Apr 2010 09:46:56 +0000 (27 11:46 +0200) | ||
| committer | Dan Carpenter <error27@gmail.com> | |
| Tue, 27 Apr 2010 09:46:56 +0000 (27 11:46 +0200) | ||
| tree | 8e68c616ec7472af1b04fadf7bcda67f851e303d | treesnapshot (tar.gz zip) |
| parent | 0b6aa23396e2253e5684f2f1f2a902b8ee1e0b40 | commitdiff |
*new* check_no_effect: print warnings statements that have no effect
I saw someone make a bug like this on lkml, but it was corrected
immediately by a reviewer. I think there might be a version of gcc that
warns about these.
This worked on my test files but when I tested the kernel I didn't find
any bugs, or any false positives.
Signed-off-by: Dan Carpenter <error27@gmail.com>
I saw someone make a bug like this on lkml, but it was corrected
immediately by a reviewer. I think there might be a version of gcc that
warns about these.
This worked on my test files but when I tested the kernel I didn't find
any bugs, or any false positives.
Signed-off-by: Dan Carpenter <error27@gmail.com>
| check_list.h | diffblobblamehistory | |
| check_no_effect.c | [new file with mode: 0644] | blob |