From: Christopher Li <sparse@chrisli.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Feature request - suppress warnings for system libraries
Date: Fri, 2 Feb 2007 14:01:48 -0800 [thread overview]
Message-ID: <20070202220148.GB27667@chrisli.org> (raw)
In-Reply-To: <1170438183.2272.29.camel@dv>
On Fri, Feb 02, 2007 at 12:43:03PM -0500, Pavel Roskin wrote:
> Hello!
>
> It would be great if sparse could optionally suppress warnings about
> system headers included using from implicit locations, such as
> "usr/include", "/usr/local/include" and GCC_INTERNAL_INCLUDE (see
> pre-process.c).
Can you be more specific about which warning you are complaining?
Point to the line of sparse code or give a small test case will be nice.
> Perhaps some major warnings could be left if they can indicate that
> sparse may have failed to parse the header properly. But the petty
> stuff should be suppressed.
>
> This would greatly help make sparse useful for code other than Linux
> kernel.
Kernel checking takes more priority. But again, it does not hurt to have
option to disable it, as long as it is off by default.
Chris
next prev parent reply other threads:[~2007-02-02 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 17:43 Feature request - suppress warnings for system libraries Pavel Roskin
2007-02-02 22:01 ` Christopher Li [this message]
2007-02-02 22:37 ` Pavel Roskin
2007-02-02 22:31 ` Christopher Li
2007-02-02 23:17 ` Al Viro
2007-02-02 23:03 ` Christopher Li
2007-02-02 23:25 ` Linus Torvalds
2007-02-03 0:30 ` Al Viro
2007-02-03 0:40 ` Al Viro
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=20070202220148.GB27667@chrisli.org \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.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).