On Fri, Sep 1, 2017 at 3:46 AM, Uwe Kleine-König <u...@kleine-koenig.org> wrote:
\>
> Nearly right. I'm responsible for the sparse Debian package and the
> problem at hand is https://bugs.debian.org/873508. This bug report has
> "Severity: serious" wihch might eventually result in the removal of
> sparse from the Debian archive.
>
> @anarcat: Given that cgcc seems to work, would you agree to apply the
> following patch to horst:
>
> diff --git a/Makefile b/Makefile
> index 4f924fa..d563652 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -110,7 +110,7 @@ $(NAME): $(OBJS)
> $(OBJS): .buildflags
>
> check:
> - sparse $(CFLAGS) *.[ch]
> + cgcc -no-compile $(CFLAGS) *.[ch]
You patch definitely works.
I think it is the better way to fix it.
Sparse "selfcheck" target was doing the same thing.
It is using "cgcc -no-compile" already.
I suggest in your patch you can do some thing
similar to "selfcheck" target:
CHECKER = cgcc -no-compile
$(CHECKER) $(CFLAGS) *.[ch]
Later when we update sparse to handle architecture
properly. We can just invoke make with "CHECKER=xxxx"
to test.
> and downgrade the bug to "important"? That would be a compromise that
> buys us a bit of time.
Agree.
>
> This only solves a part of the problem because the bug report is about
> sparse itself, not it's llvm part.
I agree with that too.
Chris
