On Mon, Jul 30, 2018 at 02:40:08PM +0200, Norbert Manthey wrote: > Dear Dan, > > I use my one-line-scan tool [1] to run smatch against non-kernel > projects. However, for Xen I still use -p=kernel, to have all the > analysis enabled. I did not write an evaluation routine to present the > defects or statistics for smatch in a nice way, but smatch can be > invoked. For the latest Xen, smatch (actually sparse) seems to struggle > with the attribute __pointer__ token, as that's not defined. > > A typical invocation for smatch would look like the following: > > export SMATCH_EXTRA_ARG="-p=kernel --file-output" > one-line-scan -o SMATCH --smatch --no-gotocc --no-analysis \ > -- make xen -j $(nproc) -B > > I will look into using the debug info next, and see how taint > information is propagated. > I tried use one-line-scan but I didn't want to install it in my $PATH so I couldn't figure out how to make it work... Then I tried to export CC=~/path/to/smatch/cgcc and HOSTCC=~/path/to/smatch/cgcc but it only builds: boot/mkelf32.c config/zconf.tab.c efi/mkreloc.c symbols.c tools/kconfig/conf.c tools/kconfig/zconf.tab.c Which is useles... 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
