Powered by Linux
Re: [PATCH] slist: Properly handle one-way merges — Semantic Matching Tool

Re: [PATCH] slist: Properly handle one-way merges

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 30, 2016 at 04:35:36PM -0400, Oleg Drokin wrote:
> BTW, speaking of the output, I wonder why is the embedded sparse output is so different from
> a stock sparse with smatch?
> I tried to also look at the stdout/err output of everything for the script parsing/warning
> of the patches in the review system and besides all warnings converted to errors,
> a bunch of warnings are totally missing and using standard sparse options cannot enable them.

It's not really running Sparse at all.  Just the minimum to parse it
into an list of statements and expressions.  In theory, it only prints
the error messages that have to do with parsing code and it doesn't do
any actual checking.

> 
> I am just trying to avoid having a double run of make and resorted to replacing a call to smatch
> with a script that calls smatch and then sparse separately, but would be even better if
> a single call to smatch would give me both outputs ;)

I tried a quick hack to make it call Sparse after calling Smatch but it
didn't work.  :/

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



[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux