Re: [PATCH 0/4] fix make sparse warning
- From
Ramsay Jones <ramsay@ramsayjones.plus.com>
- Date
- Apr 26, 2020, 16:24 UTC
- Message-ID
- <45522b6a-76a4-a7d9-3cce-a3581aaca899@ramsayjones.plus.com>
- In-Reply-To
- <20200426033201.GA14800@danh.dev>
On 26/04/2020 04:32, Danh Doan wrote:
Show 22 quoted lines
> On 2020-04-25 15:13:53+0200, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote: >> Hi Danh, >> >> On Thu, 23 Apr 2020, Đoàn Trần Công Danh wrote: >> >>> It's happened that I tried to run make check on project that support autoconf. >>> Git's Makefile told me to run `make sparse` instead. >>> >>> I /think/ if we have a rule in Makefile, we should adhere to it. >>> I also fix another change in ds/blame-on-bloom, which I think it's worth to >>> fix, see: <20200423133937.GA1984@danh.dev> >> >> FWIW there is still an Azure Pipeline building `sparse` for Ubuntu every >> two weeks: https://dev.azure.com/git/git/_build?definitionId=10&_a=summary >> >> I created this Pipeline in order to support the proposed project at >> https://github.com/gitgitgadget/git/issues/345 which is: teach our CI >> builds to run `make sparse`. >> >> Maybe it is time to tackle that? > > I don't think it's ready, yet!
Heh, not too long ago, the 'master' and 'next' branches were 'sparse clean'. (on non NO_REGEX builds anyway, and even on those for some of us. ;-) ) The 'pu' branch was frequently 'unclean', of course.
ATB, Ramsay Jones
Show 19 quoted lines
>
> May be it's.
>
> But we'll need
>
> make sparse |
> grep -v -e 'plain integer as NULL pointer' \
> -e 'redeclared with different type'
>
> The first one for:
>
> struct foo val = { 0 };
>
> to zero structure.
>
> The second one for different in declaration and definition (which is
> fixed in sparse's master).
>
>