Re: [PATCH 0/1] Using sparse in a CI job

2019-02-03 Thread Ramsay Jones
On 03/02/2019 12:12, SZEDER Gábor wrote: > On Sun, Feb 03, 2019 at 01:49:37AM +, Ramsay Jones wrote: >> On 02/02/2019 00:41, SZEDER Gábor wrote: >>> On Fri, Feb 01, 2019 at 09:01:20PM +, Ramsay Jones wrote: At the moment, on Linux, the sp-out file is free from any sparse errors

Re: [PATCH 0/1] Using sparse in a CI job

2019-02-03 Thread Ramsay Jones
On 01/02/2019 22:40, Luc Van Oostenryck wrote: > On Fri, Feb 01, 2019 at 09:01:20PM +, Ramsay Jones wrote: >> >> I suspect that the Makefile sparse target is not easy to use in a CI >> job, since the 'sparse' program (via cgcc -no-compile) does not exit >> with a non-zero value, even when is

Re: [PATCH 0/1] Using sparse in a CI job

2019-02-03 Thread SZEDER Gábor
On Sun, Feb 03, 2019 at 01:49:37AM +, Ramsay Jones wrote: > On 02/02/2019 00:41, SZEDER Gábor wrote: > > On Fri, Feb 01, 2019 at 09:01:20PM +, Ramsay Jones wrote: > >> At the moment, on Linux, the sp-out file is free from any sparse errors > >> or warnings. So are next and pu: > >> > >> $

Re: [PATCH 0/1] Using sparse in a CI job

2019-02-02 Thread Ramsay Jones
On 02/02/2019 00:41, SZEDER Gábor wrote: > On Fri, Feb 01, 2019 at 09:01:20PM +, Ramsay Jones wrote: [snip] >> At the moment, on Linux, the sp-out file is free from any sparse errors >> or warnings. So are next and pu: >> >> $ grep error sp-out >> $ grep warning sp-out > > On 'master

Re: [PATCH 0/1] Using sparse in a CI job

2019-02-01 Thread SZEDER Gábor
On Fri, Feb 01, 2019 at 09:01:20PM +, Ramsay Jones wrote: > I suspect that the Makefile sparse target is not easy to use in a CI > job, since the 'sparse' program (via cgcc -no-compile) does not exit > with a non-zero value, even when issuing errors and warnings. We had the same issue with Coc

Re: [PATCH 0/1] Using sparse in a CI job

2019-02-01 Thread Luc Van Oostenryck
On Fri, Feb 01, 2019 at 09:01:20PM +, Ramsay Jones wrote: > > I suspect that the Makefile sparse target is not easy to use in a CI > job, since the 'sparse' program (via cgcc -no-compile) does not exit > with a non-zero value, even when issuing errors and warnings. ... > We can change that

[PATCH 0/1] Using sparse in a CI job

2019-02-01 Thread Ramsay Jones
I suspect that the Makefile sparse target is not easy to use in a CI job, since the 'sparse' program (via cgcc -no-compile) does not exit with a non-zero value, even when issuing errors and warnings. The way I use sparse, this is not an issue. I run sparse over the master branch, check that the