Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx> writes: > Having said that, I rarely run sparse over just one file (except > when fixing a sparse error/warning). On each branch (master->next->pu) > I do > > $ make sparse >sp-out 2>&1 # nsp-out on 'next', psp-out on 'pu' > > ... so that I can diff the files from branch to branch. (I check the > master branch file by hand. There is a single warning on Linux that > is actually a sparse problem). > > Just FYI, for today's fetch: > > $ diff sp-out nsp-out > $ diff nsp-out psp-out > 12a13 > > SP blame.c > 42a44,46 > > diff.c:813:6: warning: symbol 'emit_line' was not declared. Should it be static? > > diff.c:828:6: warning: symbol 'emit_line_fmt' was not declared. Should it be static? > > diff.c:1865:6: warning: symbol 'print_stat_summary_0' was not declared. Should it be static? > 54a59 > > SP fsmonitor.c > 137a143 > > SP sub-process.c > 170a177 > > SP compat/fopen.c > 276a284 > > builtin/worktree.c:539:38: warning: Using plain integer as NULL pointer > 296a305 > > SP t/helper/test-dir-iterator.c > $ Interesting. One thing that I found somewhat suboptimal is that we do not get signalled by non-zero exit. Otherwise it would make a good addition to the "Static Analysis" task in .travis.yml file.