On Thu, Jun 14, 2012 at 12:53:52AM -0400, KOSAKI Motohiro wrote: > Hi, > > Today, I tried to use 'smatch' for ruby project and I found plenty false positive errors. > They were mainly caused that glibc uses some no smatch recognized attributes. I did apply > following patch myself. (see below) > > Is there any more good way? I didn't find a hint from README. > > And, I have one unsolved issue. I've seen following annoying error a lot. > > /usr/include/bits/xopen_lim.h:122:6: warning: constant 9223372036854775807L is so big it is long long > > Because of, /usr/include/limits.h has "#define LONG_MAX 9223372036854775807L" and it is completely > valid on 64bit OS. Is there any way to disable this message when using 64bit? The way to do this is to add an -m64 to the cgcc command. make CHECK="~/path/to/smatch/smatch --full-path" \ CC="~/path/to/smatch/cgcc -m64" And it also does seem like Smatch prints out a bunch of garbage... I'll try turn of it off unless the --spammy flag is used. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe smatch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
