From: Pavel Roskin <proski@gnu.org>
To: linux-sparse@vger.kernel.org
Subject: Feature request - suppress warnings for system libraries
Date: Fri, 02 Feb 2007 12:43:03 -0500 [thread overview]
Message-ID: <1170438183.2272.29.camel@dv> (raw)
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).
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.
--
Regards,
Pavel Roskin
next reply other threads:[~2007-02-02 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 17:43 Pavel Roskin [this message]
2007-02-02 22:01 ` Feature request - suppress warnings for system libraries Christopher Li
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=1170438183.2272.29.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.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).