From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Kees Cook <keescook@chromium.org>,
Miroslav Benes <mbenes@suse.cz>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sparse warnings in overflow.h
Date: Fri, 8 Jun 2018 01:45:34 +0200 [thread overview]
Message-ID: <20180607234533.nfdxd4cqiygahfms@ltop.local> (raw)
In-Reply-To: <4d2aaa98-1655-3ab8-8ce8-bf4b9c7d2dbc@rasmusvillemoes.dk>
On Thu, Jun 07, 2018 at 09:25:09PM +0200, Rasmus Villemoes wrote:
>
> IIRC, the problem is that sparse pretends to be the gcc sparse itself
> was built with, which is obviously entirely unrelated to the C dialect
> that that particular sparse version groks. Sigh. Ack to the fix above.
Yes, indeed, and it is sometimes a problem.
Ideal would be that sparse would pretend to be same GCC as the one used
to compile the code being checked *and* to have exactly the same features.
Pretending to be an older version of GCC would maybe solve the present
problem it's not really a general solution.
One good thing would be to not depend on GCC versions to enable some
features (but GCC offers few facilities helping here).
Best regards,
-- Luc Van Oostenryck
next prev parent reply other threads:[~2018-06-07 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 11:01 sparse warnings in overflow.h Miroslav Benes
2018-06-07 18:35 ` Kees Cook
2018-06-07 19:25 ` Rasmus Villemoes
2018-06-07 23:45 ` Luc Van Oostenryck [this message]
2018-06-08 6:34 ` [PATCH] compiler-gcc.h: don't set COMPILER_HAS_GENERIC_BUILTIN_OVERFLOW for sparse Miroslav Benes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180607234533.nfdxd4cqiygahfms@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mbenes@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.