From: Pavel Roskin <proski@gnu.org>
To: Pierre Habouzit <madcoder@debian.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: feature-request
Date: Sun, 24 Feb 2008 21:48:45 -0500 [thread overview]
Message-ID: <1203907725.25518.17.camel@dv> (raw)
In-Reply-To: <20080223133945.GB10967@artemis.madism.org>
On Sat, 2008-02-23 at 14:39 +0100, Pierre Habouzit wrote:
> While I'm at it, there is this feature I'd like to see in sparse: I'd
> love to be able to ask it to ignore errors that are located in some
> specific paths (like /usr/include e.g.). For now I'm doing that through
> a custom script, but it'd be simpler for me if it does it natively. The
> reason is that I don't want to patch third party libraries headers.
We probably don't want to ignore _errors_, as they can indicate that the
parser doesn't understand the code correctly. Ignoring warnings would
be a good idea.
Perhaps a simpler approach would be to turn off warnings in any files
included using angle brackets.
gcc doesn't report warnings in system files by default, but it can be
enabled with -Wsystem-headers. Since sparse is primarily for the
kernel, I think the default should be to check the headers (as they are
part of the kernel), but sparse could support -Wno-system-headers.
Alternatively, sparse could have a userspace mode that would disable
warnings in system headers by default (unless -Wsystem-headers is used).
The kernel mode could be made stricter for the kernel without affecting
the userspace.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-02-25 2:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 13:39 feature-request Pierre Habouzit
2008-02-25 2:48 ` Pavel Roskin [this message]
2008-02-25 8:54 ` feature-request Pierre Habouzit
2008-02-25 14:22 ` feature-request Pavel Roskin
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=1203907725.25518.17.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.org \
--cc=madcoder@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).